-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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 beta] Add failing test for issue 16172 #16284
Closed
kennethdavidbuck
wants to merge
12
commits into
emberjs:beta
from
kennethdavidbuck:failing-test-for-issue-16172
Closed
[BUGFIX beta] Add failing test for issue 16172 #16284
kennethdavidbuck
wants to merge
12
commits into
emberjs:beta
from
kennethdavidbuck:failing-test-for-issue-16172
Conversation
This file contains 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
(cherry picked from commit a3ba91f)
Previously, any errors thrown during `didInsertElement` would leave the running environment in an invalid state (`env.inTransaction` would be `true` but `this._transaction` would have been nullified). This commit ensures that we _always_ reset `inTransaction` if `Environment.prototype.commit` is called. Thus avoiding an error RE: "calling commit on null"... (cherry picked from commit ab4a2e3)
(cherry picked from commit e99dd89)
`Ember.trySet` is designed to be an error-tolerant form of `Ember.set` (per its public API documentation). However, in some circumstances an error is still thrown when setting on a destroyed object. Prior to this change, the following would properly prevent an error: ```js let obj = { some: { deep : 'path', isDestroyed: true }}; Ember.trySet(obj, 'some.deep', 'stuff'); ``` But the following would throw an error incorrectly: ```js let obj = { some: 'path', isDestroyed: true }; Ember.trySet(obj, 'some', 'stuff'); ``` This fixes the latter case... (cherry picked from commit 1f4a3bc)
[ci skip]
Closed by #17003 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add a failing test for issue #16172