Unneccessary field suggested in content type

[willphdavies]

Content types are required to have a text field as the first field, if they do not a warning shows.

There are many instances where a content type does not need a text field, but one has to be added anyway resulting in a confusing extra field

[travism]

Will, we use the text field as a label. It's used more than it seems. There may be some exceptions when it isn't needed but most of the time it helps.

[Duder-onomy]

Chiming in again. Just trying to help.

@willphdavies Travis is correct, the warning was put in as the 'title' of the content is used throughout admin, on the table views and the header of the accordion on embedded types for example. If the first field is not a string or string-like, then Admin cannot show the name in a reasonable way.

Admin assumes the first field on the content type is the label for the content.

If the string is not good enough, you can use the template plugin and make the title a computed value of other fields on the content. Like, if you wanted the title to be ${sku}-{somethingElse} you could do that...maybe that makes more sense for your use case?

Anyhow, the code that does this check is in the _saveContentWorkflow method of the contentTypeDetailView You can see a call to '_warnIfFirstFieldIsNotString'