-
Notifications
You must be signed in to change notification settings - Fork 963
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 loadDerived
not taking entity cache into consideration when loading derived entities
#4799
Fix loadDerived
not taking entity cache into consideration when loading derived entities
#4799
Conversation
…derived_entities
b9cd862
to
259cda0
Compare
2325994
to
0371ee2
Compare
0371ee2
to
9c41c38
Compare
817d61f
to
f70ee0e
Compare
f70ee0e
to
626890b
Compare
f248968
to
c7bce0d
Compare
|
||
for (key, entity) in entity_map.iter() { | ||
// Only insert to the cache if it's not already there | ||
// This is to avoid overwriting updates |
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.
Since self.current
only contains entities that have already been written to the store, there's no danger of clobbering an update. It's still good to add those entities to self.current
, it's just that the comment is misleading.
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.
in that case should we just insert it without checking ? Is there a reason to keep the check?
@lutter Any idea why the runner tests are failing with |
The runners test issue was a yarn workspace issue. fixed it |
Closes #4727