[BUGFIX release] Ensure _actions
specified to extend works.
#12188
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.
The initial deprecation of
_actions
and moving it toactions
was a bit too naive. ThedeprecateProperty
helper was used, which meant that when_actions
was set, it would callset(this, 'actions', newValue)
. This meant that passing_actions
toEmber.Route.extend
(or.reopen
) resulted in the_actions
completely clobberingactions
(and loosing any previously defined actions there).The fix was to:
deprecateProperty
usage with a customObject.defineProperty
call, that defines a setter with an assertion instead of clobbering.willMergeMixin
that mutates theprops
at extend time (to ensure that_actions
is moved toactions
with a deprecation).Fixes #12081.
Thanks to @kimroen for helping track this down.