QueryParams not recognized (e.g. on store.filter) about ember-cli-mirage HOT 7 CLOSED

I see, can you show me the route you defined in config.js?

from ember-cli-mirage.

Sure (don't mind the non-get verbs):

  this.get('languages');
  this.get('languages/:id');
  this.post('languages');
  this.put('languages/:id');
  this.delete('languages/:id');

Prerably, if query params are detected, it would be great to handle them in a callback; or with a filter on the collection by default!?

from ember-cli-mirage.

Yep this is a bug, it should get the languages collection and let you work
with the query params via request.params. I'll check it out.
On Fri, Mar 27, 2015 at 5:01 AM jens alexander ewald <
[email protected]> wrote:

Sure (don't mind the non-get verbs):

this.get('languages');
this.get('languages/:id');
this.post('languages');
this.put('languages/:id');
this.delete('languages/:id');

Prerably, if query params are detected, it would be great to handle them
in a callback; or with a filter on the collection by default!?

—
Reply to this email directly or view it on GitHub
#66 (comment)
.

from ember-cli-mirage.

@jens-a-e fixed in master, you can use now with this in your package.json:

"ember-cli-mirage": "samselikoff/ember-cli-mirage"

from ember-cli-mirage.

👍 nice! thx for the quick fix!!

from ember-cli-mirage.

I think this might be broken in 0.0.27. I'm seeing the following in my application:

Mirage: The route handler for /api/v1/activity_responses?focused=true&membership_id=1 is requesting data from the activity_responses collection, but that collection doesn't exist. To create it, create an empty fixture file or factory.

from ember-cli-mirage.

Never mind! I made a mistake.

from ember-cli-mirage.