-
-
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
Relationship Refactor (part-1) #7491
Conversation
ac84767
to
52ce23c
Compare
Asset Size Report for 66f5e79 IE11 Builds 🛑 The size of the library EmberData has increased by +2.75 KB (+481.0 B compressed) which exceeds the failure threshold of 75 bytes.WarningsChangeset
Full Asset Analysis (IE11)
Modern Builds 🛑 The size of the library EmberData has increased by +2.86 KB (+434.0 B compressed) which exceeds the failure threshold of 75 bytes.WarningsChangeset
Full Asset Analysis (Modern)
Modern Builds (No Rollup) 🛑 The size of the library EmberData has increased by +2.87 KB (+575.0 B compressed) which exceeds the failure threshold of 75 bytes.WarningsChangeset
Full Asset Analysis (Modern)
|
52ce23c
to
fc731d3
Compare
Performance Report for 66f5e79 Scenario - materialization: ✅ Performance improved
Scenario - unload: ✅ Performance improved
Scenario - destroy: ✅ Performance improved
Scenario - add-children: ✅ Performance improved
Scenario - unused-relationships: ✅ Performance improved
|
flatten belongs-to relationship fix: implicit inverse key gen needs to utilize the related type for uniqueness
07c659c
to
66f5e79
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:nods again
The overall direction here is towards the edges not managing their inverses and state.
Relationships
class (this is a small perf improvement) in favor of dictionaries managed directly by the cache.rhs/lhs
info cache from the lazy-relationship cache in ember-data 3.4 has been revived with some improvements. This is in part to support polymorphism and in part to support coming perf improvements to the relationship layer that are akin to why we needed these infos for the lazy-relationship cache.@jrjohnson is investigating why this potentially caused an error in
ilios/frontend
.The improved assertions for polymorphism caught a test in
ember-data-storefront
that has an incorrect polymorphism configuration. The fact that a few of our own tests as well as this storefront test could pass in the past is evidence that we could potentially just delete all the assertions at this point.