-
-
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
Query arity check fails, leading to recordArray/options being dropped #6232
Labels
🏷️ bug
This PR primarily fixes a reported issue
Comments
The resolution here is to drop the arity check entirely as there is no longer a way to do this when things extend from TL;DR |
@runspired @malatin3 I took a stab at this in #6250. |
runspired
pushed a commit
that referenced
this issue
Jul 15, 2019
This addresses the issue described in #6232. The arity check that decides whether to create a record array and pass options to adapter.query fails when the adapter extends EmberObject.
pete-the-pete
pushed a commit
to pete-the-pete/data
that referenced
this issue
Jul 23, 2019
This addresses the issue described in emberjs#6232. The arity check that decides whether to create a record array and pass options to adapter.query fails when the adapter extends EmberObject.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reproduction
@runspired is aware of the specific issue here and said that reproduction steps are unnecessary for this issue.
Description
In the underlying
_query()
function used when callingstore.query()
, it makes an arity check for the number of arguments ofquery()
in the adapter to see if it should pass alongrecordArray
andoptions
as fourth and fifth parameters. However, this length check does not work unless native classes are used. In a local test case, even when the adapter hasquery(store, type, query, recordArray, options)
, this check sees it as asuperWrapper
with a length of 0. This causes it to only pass along thestore
,type
, andquery
arguments, and it doesn't create/pass a record array, nor does it pass options.According to @runspired, this appears to have been broken since 3.2.
Versions
The text was updated successfully, but these errors were encountered: