-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Perf: Refactor PromiseManyArray and prep for RFC#745 #7505
Conversation
Asset Size Report for f993c2b IE11 Builds 🛑 The size of the library EmberData has increased by +4.32 KB (+715.0 B compressed) which exceeds the failure threshold of 75 bytes.Warnings
Changeset
Full Asset Analysis (IE11)
Modern Builds 🛑 The size of the library EmberData has increased by +3.74 KB (+685.0 B compressed) which exceeds the failure threshold of 75 bytes.Warnings
Changeset
Full Asset Analysis (Modern)
Modern Builds (No Rollup) 🛑 The size of the library EmberData has increased by +3.55 KB (+619.0 B compressed) which exceeds the failure threshold of 75 bytes.Warnings
Changeset
Full Asset Analysis (Modern)
|
11d6e76
to
8efd03c
Compare
Performance Report for f993c2b Scenario - materialization: ☑️ Performance is stable
Scenario - unload: ✅ Performance improved
Scenario - destroy: ✅ Performance improved
Scenario - add-children: ☑️ Performance is stable
Scenario - unused-relationships: ☑️ Performance is stable
|
packages/-ember-data/tests/integration/relationships/nested-relationship-test.js
Outdated
Show resolved
Hide resolved
The list of items in the PR title is a bit confusing, as |
de602e7
to
9902a52
Compare
fa98b30
to
4769580
Compare
96adf26
to
cb146ae
Compare
e316b48
to
8bb156e
Compare
6c760cf
to
acd7a3e
Compare
31d3869
to
010b63c
Compare
8bb156e
to
3291671
Compare
0914e86
to
e6bbdf1
Compare
This allows us to remove the sync-flush of ManyArray by utilizing a custom enumerable instead of ArrayProxy which was installing array observers. We now only sync-flush if array observers are added by an application.
Refactored in a way that adding deprecations from emberjs/rfcs#745 should be trivial, though will require test changes to resolve any deprecations it results in for our own app (I have a branch with those changes for when the time comes)