-
-
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
chore: InternalModel burndown #8078
Conversation
Asset Size Report for e9fe99f Modern Builds ✅ EmberData shrank by -183.0 B (-317.0 B compressed)Warnings
Changeset
Full Asset Analysis (Modern)
Modern Builds (No Rollup) ☑️ EmberData has not changed in sizeIf any packages had changed sizes they would be listed here. Changeset
Full Asset Analysis (Modern)
|
Performance Report for e9fe99f Scenario - materialization: ☑️ Performance is stable
Scenario - unload: ✅ Performance improved
Scenario - destroy: ✅ Performance improved
Scenario - add-children: ✅ Performance improved
Scenario - unused-relationships: ✅ Performance improved
|
…of which is probably a delete case
Just curious, does this mean that there are plans to remove the concept of async relationships? |
@sandstrom yes! Hopefully for 5.0 this fall (see #8086) but definitely within the year. Basically any replacement to |
Picks up where #8055 left off
Big goal for this PR is to get relationship state classes out of core and into the model package. A still unanswered question is what to do with references. This has been a circular debate on the core team in the past, the war of attrition suggests my path forward is the one we take (references should die with @ember-data/model) though I'm open to other paths forward. My reasoning is that directly asking the cache for relationship information is more useful, and we can expose the Graph as public API in the future if we so choose (again more useful). References were always little more than a workaround for the messiness of async relationships, and if those are dying anyway there's not much reason to keep them around in my mind.
Important release note: users of only the core of ember-data (for instance users of ember-m3) can expect the total size to shrink between 35-50% once upgrading to a release with these changes and those in #8055