Add "default" value to field settings selection and define global defaults settings per display mode

Is any work happening @thomas.frobieter? It's assigned to you.

Is there a current workaround if I want the default for all elements and wrappers to be "None"?

Open for the community. We'll proceed here as soon as we have the time.

Is there a current workaround if I want the default for all elements and wrappers to be "None"?

@John Pitcairn Not a clean one, unless you write a patch and override the default.
Maybe the easiest way for you is to override the twig file, and find a condition that works for you until this is fixed.

Maybe use attributes.hasClass('x'), if your class 'x' is not set, do not print the field_tag.
{{ field_tag|default('div') }}

You know... dirty workaround, but hopefully it helps for now.

Ha. I mean the default in the formatter, where defaults are currently hard coded. Probably has to be add an #after_build callback to the entire form.

This whole opening, closing and creating of issues, got everyone confused, I think.

This: ✨ Allow to define presets for typical configurations (fences_presets submodule) Active is the main issue, where we are going to implement this feature. As soon as we are able to create "Preset" config entities, we can have a default preset entity on install, which can be manually overwritten if needed, or you can add your own preset through a custom config.yml.

I'll close this issue but leave a reference to it for future development in ✨ Allow to define presets for typical configurations (fences_presets submodule) Active .