Fix 'firstObject/lastObject' properties in Ember 4 with native proxies #1726
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.
Root Cause Analysis
Ember 4.x replaced
arrayContentDidChange
with another function whereas the state of 'firstObject/lastObject' were left open.What has changed
Added a test cases to reproduce the issue and verify the fix.
Fixed the issue by changing how
firstObject
andlastObject
get its value.Testing Done
yarn test
passed locally.@co-authored-by hjdivad