Replies: 1 comment 3 replies
-
Thank you for raising this @erlando. In recent years, my general stance with my code is to mark it Thanks for the prompt, I'm happy to open up some of the constants. I'll give it some thought on how to best go about it, as my initial thought is not to change the |
Beta Was this translation helpful? Give feedback.
-
Internally Contentment uses its own editors for config. This makes complete sense. Contentment has constants for configuration field aliases and editor view paths but alas they are internal and cannot be used by 3rd party implementations.
I would like to suggest that Constants.Conventions.ConfigurationFieldAliases be made publicly accessible.
It would also be nice if the View member had a static pendant such that you do not have to do things like this
View = _ioHelper.ResolveRelativeOrVirtualUrl(new CheckboxListDataListEditor().View)
when setting up a configuration field for a data source. It just seems.... wrong somehow :-)Lastly, thank you for a very nice package.
Beta Was this translation helpful? Give feedback.
All reactions