James Pulec
James Pulec
PR in #112
Is this seen as a non-standard use case, or that it breaks expected behavior?
I'm wondering if it makes sense to allow disabling this via an environment variable. Something that is off by default, but could be set to allow lockfile discrepencies, i.e. `YARN_IMMUTABLE=false`.
I think this is still a feature worth having. Providing a sql based segment to allow filtering feels like a much better experience for your users, instead of requiring them...
@jasonkuhrt I just modified one of the existing tests to use a custom primary key name. Hope that's kinda what you're looking for.
Closing as this doesn't seem to be actively matina
I'm also seeing this behavior, and I can consistently reproduce it if I try to access an endpoint that streams data back from multiple browser tabs in parallel. This is...
If you wish for that behavior you need to defined `Post` like so: ``` javascript Post: restmod.model(); ``` Note the absence of a scoped url for the Child relationship.
You don't want to be mixing `belongsTo` and `hasOne`. Those are two different styles of relations. You would want to define it like the following: ``` javascript var Trailer =...
The result of `Bike.$search({brand: 'Trek'})` should be a restmod `Collection`. A `Collection` contains individual instances of `Bike`. What does more of your code look like?