You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
adapterOptions is a great way to communicate one-off settings to an adapter; however, it does not appear that it is usable for query or queryRecord.
Here is a demonstration on how passing adapterOptions into the query argument for store.query and store.queryRecord will just result in the options being parameterized (which according to the docs is exactly what should be happening -- it mentions directly passing on anything present there).
I would assume there are a few paths forward:
allow adapterOptions to be passed into the query argument for store.query and store.queryRecord, automatically strip that key and provide it to the snapshot, and then update the docs to document that special behavior
allow a third options argument to store.query and store.queryRecord
????
The text was updated successfully, but these errors were encountered:
adapterOptions
is a great way to communicate one-off settings to an adapter; however, it does not appear that it is usable forquery
orqueryRecord
.Here is a demonstration on how passing
adapterOptions
into thequery
argument forstore.query
andstore.queryRecord
will just result in the options being parameterized (which according to the docs is exactly what should be happening -- it mentions directly passing on anything present there).I would assume there are a few paths forward:
adapterOptions
to be passed into thequery
argument forstore.query
andstore.queryRecord
, automatically strip that key and provide it to the snapshot, and then update the docs to document that special behavioroptions
argument tostore.query
andstore.queryRecord
The text was updated successfully, but these errors were encountered: