-
-
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
[Cache] attributes of records got missing #8519
Comments
can you push this to the repo? I'll want to debug it |
Sorry for not mention it. I've already done that. |
Currently, the CacheHandler only instantiates records in the response documents for I suspect there's also some more documentation to add here around where/how to do what kinds of work. |
No worries, figured that out |
With some changes and upgrade to
alpha.15
I accidentally bypassed theCache
so I added theCacheHandler
back into myrequestManager
service and now thecache
is hit again. Because the response is JSON, I extended theCache
and converted the JSON into JSONAPI data so that the default JSONAPI cache consumes the data.This worked prior to
alpha.15
. In my template I had to add theattributes
key but that's ok. I also tested it with converting the response directly after thefetch
but it doesn't make a difference.BTW, also the
instantiateRecord
isn't called when doing astore.findAll(model)
orstore.query(model, options)
so some wire seems to be broken.The text was updated successfully, but these errors were encountered: