We can duplicate default value management at for display edit screens, then it becomes more natural

Also link from widget edit form should point to place where default value could be changed

still I find it weird to manage the default status of this field on the CT editition when you can also configure it on the form display

Comments

andypost created an issue. See original summary.

attiks’s picture

attiks commented
Issue summary: View changes

Any change we can have a patch?

andypost’s picture

andypost
he/him
Primary language Russian
commented
Related issues: +#1919834: Field instance got no default value when created in field UI, +#552604: Adding new fields leads to a confusing "Field settings" form

First it needs #1919834: Field instance got no default value when created in field UI
then sort of #552604: Adding new fields leads to a confusing "Field settings" form

drugan’s picture

drugan commented

I also think the same way. Field config settings (not storage) need to be duplicated (or moved?) on the relative widget/formatter settings page. Current adding new field algorithm is a bit confusing for newcomers as it two times suggests to Save field settings. After that user will go to Manage display and Manage form display tabs and see more settings some of which are the same as on the Edit field tab.

My first experience on adding a field is that: Why they have so many **settings**? Which one is the main?

1. Field config settings have to be clearly separated from the field storage settings.

2. Do we need global field config settings applied on all the field's form display and display modes? I think that this is a bit redundant and again, confusing. What we really need is just **per mode** widget/formatter settings which purpose is easy to understand and manage. And not only for users but for developers too will be better to have code for a field settings in one place without need to sync changes on the code across the whole system. As an example is field placeholder setting duplicated on both field base definition and field widget classes.

There is some attempt to achieve all the above for the number field's widget. Just try and see the difference.