Wade Tandy

Makes sense and I agree that we should not change the defaults. If we're doing some nice things on behalf of `nil`, it might be a good idea to do...

In general I would Be in favor of either allowing nil and undefined OR allowing neither, but I’m not going to get too worked up about any outcome here.

As this is specific to inheriting ID from the parent, we could also do this with a class attribute (on mobile so forgive formatting): ApplicationResource self.default_id_type = :uuid end

These are by default what gets called under the hood when you have an attribute filtered by the specified operator: ```ruby class PostResource < ApplicationResource attribute :title, :string, filterable: true...

>as long as we have a cursor-like implementation it doesn't matter to us whether it's offset-oriented or stable ids This is a really good point from a usability perspective. Maybe...

@mkamensky There's a few ways to go about this, and depending on what you want I think this can be approached in different ways. If you specifically want to be...

I have been running into this issue this week while looking at moving our product to using `beforeRouteEnter` guards to preload data. Seems this becomes a non-starter from a development...

Looks like a good fix! Would you mind adding a corresponding spec too?

> Since we generate the models from the schema, it's not tedious for us to do this. 👀 Would love to see anything that you have in this arena if...

Oh yeah i totally missed this as well, sorry about that. Will take a look.