[Backport] Naming collision in Javascript ui registry (backend)#15289
Merged
magento-engcom-team merged 1 commit intomagento:2.1-developfrom Jun 20, 2018
Conversation
VitaliyBoyko
added
backport
partners-contribution
DanielRuf
approved these changes
May 17, 2018
Contributor
|
Hi @VitaliyBoyko. Thank you for your contribution. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Original PR: #12945
Description
The JS is broken in next case: when the new configurable attribute is created with the code name that is equal to "index" property of any uiComponent on the page.