-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shape type naming convention #5151
Comments
Related #5126 Also, All Parts in Form Modules, e.g |
Might not be necessary anymore as JT found a solution to the issue that triggered this suggestion. But the editor/display mode part is still valid. |
possible fix for the editor/display explicit registration on #4361 |
Is there anything still necessary here? |
It seems that this issue didn't really move for quite a while. Is this something you'd like to revisit any time soon or should we close? Please reply. |
Closing this issue because it has been stale for very long. If you think this is still relevant, feel free to reopen it. |
[Stereotype]_[DisplayType]__[Subject]
Each element should not contain
__
or_
.Example:
Content_SummaryAdmin__ActionButtons
instead ofContent_SummaryAdmin__Button__Actions
For editor/display modes, we should use explicit driver registrations, which will drive the shapes to edit/display following the same rule.
The text was updated successfully, but these errors were encountered: