Problem/Motivation
In the current situation, all extra settings defined by the plugin manager are enable by default and can be hidden per field instance. When adding an extra option, users need to go to all fields to disable it. Since most settings will not be used in the majority of use cases, this could lead to confusing interfaces where extra options are shown to the user.
Proposed resolution
It would be better to hide the settings by default and allow field instances to op-in. So switch from 'Hide settings' configuration to 'Enable extra settings' when configuring the field.
Remaining tasks
Change the configuration option for field instances.
Use the option in the field widget
Use the option in the formatter
Change update hook to enable the title/argument options for users upgrading from 1.x
User interface changes
Changed 'Hide settings' configuration to 'Enable extra settings' when configuring the field.
API changes
-
Data model changes
-
Comments
Comment #3
seanbAdded issue for reference purposes. Fixed and pushed to 2.x.