This was raised in a comment to issue 243.
A custom-entity-level settings object - so each custom entity type gets a single settings object, again with the purpose of allowing the editor to specify common labels, error messages etc for all instances of that custom entity. My naïve expectation for how this might be defined would be something like MyCustomEntity : ICustomEntityDefinition<MyCustomEntityModel, MyCustomEntitySettings>
So using a "Blog Post" custom entity as an exampe, a developer would want to definine a corresponding blog post settings model to define global settings for all blog post custom entities e.g. translations for global terms like "Blog Post" or a configuration setting like the page size to use on the list page.
I don;t think we'd want to use generics on the definition type as suggested in the comment as extra generic types can cause more problems, but some other type reference could be used. There would also need to be a new way to access the configuration settings - perhaps accessed from the custom entity list page.
This was raised in a comment to issue 243.
So using a "Blog Post" custom entity as an exampe, a developer would want to definine a corresponding blog post settings model to define global settings for all blog post custom entities e.g. translations for global terms like "Blog Post" or a configuration setting like the page size to use on the list page.
I don;t think we'd want to use generics on the definition type as suggested in the comment as extra generic types can cause more problems, but some other type reference could be used. There would also need to be a new way to access the configuration settings - perhaps accessed from the custom entity list page.