Skip to content
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

bugfix: handle null and undefined in setProperties #1417

Merged
merged 1 commit into from
Jun 15, 2023

Conversation

chriskrycho
Copy link
Contributor

This implicitly worked for as long as this.setProperties existed, because it ultimately forwards to Ember's setProperties, which also implicitly works with this. Although this is not public API, and indeed is not desirable, changing it (implicitly and accidentally!) will break many consumers who are relying on it (most likely to end up happening transitively, e.g. via local/custom test helpers).

This implicitly worked for as long as `this.setProperties` existed,
because it ultimately forwards to Ember's `setProperties`, which also
implicitly works with this. Although this is not public API, and indeed
is not desirable, changing it (implicitly and accidentally!) will break
many consumers who are relying on it (most likely to end up happening
transitively, e.g. via local/custom test helpers).
Copy link
Sponsor Collaborator

@NullVoxPopuli NullVoxPopuli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the tests, comments, and explanation!

@NullVoxPopuli NullVoxPopuli merged commit 77a71be into master Jun 15, 2023
16 checks passed
@NullVoxPopuli NullVoxPopuli deleted the preserve-setProperties-behavior branch June 15, 2023 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants