In version 3.x, there was a label associated with each field in the field settings form since all the form logic was handled there but when we split out some settings to the manage form display, an assumption was made that the field labels would be handled there. However, core fields do have a label in field settings that serve as basically a default value for manage display & manage form display labels so we should follow suit to make the UX simpler and assume the labels in those sections are for overrides.
Without a sub-field settings label, it may be confusing to users to know that these can be overridden in the display sections and seemingly some people for whatever reason never even visit those sections and just assume the default widgets / formatters. I don't know why that would happen in normal setups but it's been brought to my attention through others demoing my module in a very high level manner, that they expect a label field here so... we will provide it for consistency with core.
Add label field back to field settings form defaulted to a user friendly altered machine name (upper case first word and replace underscores with spaces). The display labels should use this value as a default if not set in their settings. Add an update hook to set this.
Active
4.0
User interface
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.