-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Conversation
- updated rules for names and aliases - renamed file to be more precise
Thanks for the work on this. |
The `name` attribute should adhere to the guidelines listed below. The `name` attribute should: | ||
|
||
- Should explain element's purpose rather than its position on the page . | ||
- Be unique to the module that declares it by prepending it with module's namespace as `<vendor>.<module>` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I like this idea. However, I'm a bit hesitant because literally none of the core does this. I was hoping to keep it compatible with at least the general principle of what is already in the core.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It can be done for the new layouts. So far it's just my idea, I'll be discussing it more. Thanks for your feedback.
I guess it wants me to sign CLA :) |
Added community member attribution to 2.2.5 release notes
@jcalcaben, can we merge this? |
@buskamuza is there a status update for this PR? |
Suggestion: what about removing this line for now? We can always add it later if the core starts drifting in this direction.
|
@melnikovi , @antonkril , please review |
Closing the proposal based on the discussion https://github.com/magento/architecture/wiki/October-31,-2018 |
This PR is a:
Summary
Original PR - #1078
Additional information