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.
Hi @joamatab , this PR makes reference naming more reliable, by replacing the
alias
andaliases
attributes with a property calledname
onComponentReference
and corresponding propertynamed_references
onComponent
. Becausenamed_references
is a calculated property, it is guaranteed to always stay in sync withComponent.references
. Becausename
andowner
are both changed to properties, we also guard against strange cases where either are changed midway through creating a component.I know the deprecation of alias/aliases may be controversial, but for now they should be smoothly deprecated with a DeprecationWarning. There should be no breaking changes, except the user is no longer allowed to explicitly set
Component.aliases
(which they never should have done anyways)