Fix bug where record rejected via find
stayed in loading state
#3043
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
store.getById(typeClass, id)
is used inside the rejection handler offind
to get the record and invoke the corresponding hooks. This isbuggy since the record is not loaded yet into the store - a successful
find
would mark it as such - and hence thestore.getById
returnednull
. That's why the hooks are not called and the record stays in theloading
state, having theisLoaded
flag still being set tofalse
.The fix is to reuse the
record
parameter, which is passed to thefind
method. By this, the hooks are invoked and the record is passedtransitioned out of the
loading
state.This partially addresses #3013