-
-
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
fix: backgroundReloads should not affect recordIsLoaded (#8125) #8128
Conversation
Asset Size Report for 5a75092 Modern Builds ✅ EmberData shrank by -203.0 B (-54.0 B compressed)If any packages had changed sizes they would be listed here. 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 5a75092 Scenario - basic-record-materialization: ☑️ Performance is stable
Scenario - relationship-materialization-simple: ☑️ Performance is stable
Scenario - relationship-materialization-complex: ☑️ Performance is stable
Scenario - unload: ☑️ Performance is stable
Scenario - unload-all: ☑️ Performance is stable
Scenario - destroy: ☑️ Performance is stable
Scenario - add-children: ☑️ Performance is stable
Scenario - unused-relationships: ☑️ Performance is stable
|
d446281
to
5a75092
Compare
Currently doesn't appear to be a regression here, but probably a good test to have around anyway. The regression might be in the timing of the promise-record setup, if so we'll need more info to track it down. Another hypothesis is there is an unloadRecord call involved which previously the findRecord call was "cancelling". Now the unloadRecord call would succeed and the data be cleared and refetch required.