Jouke van der Maas

This is not possible at the moment, but I'm open to a PR to allow this. The request URI comes from here: https://github.com/joukevandermaas/saule/blob/41c9b84a0158bfa2b633e4023a15f2a24e8dcc0d/Saule/Http/PreprocessingDelegatingHandler.cs#L59 It's then passed into the serializer here:...

I agree with you, but it currently does not have this behavior. So that would be breaking backwards compatibility. If you can think of a way to not break existing...

It doesn't really seem to fit very nicely in the JSON api spec to do such a thing. Especially since the `$type` value must be the *first* value in the...

@bjornharrtell looks like a good approach. It's not very clear from the examples on the page you linked, but it seems that you should be able to post/patch/delete resources of...

I think it's probably not supported yet, but you might be able to get it working using custom filter expressions. See [here](https://github.com/joukevandermaas/saule/wiki/Queryable-endpoints#customizing-filtering-expressions) for more info. I assume the value you'd...

It isn't. I'm open to a PR but I don't have time to pick this up ATM.

@PhyberApex I don't think we need to support escaping commas to be honest. If the spec doesn't mention it, it shouldn't be blocking us IMO.

I suppose we could do like in CSV? So if the filter string is in quotes, we don't interpret the commas? `?filter[prop]="some,value"` => checks that `prop` is `"some,value"`. `?filter[prop]=some,value` =>...

It would be like `?filter[prop]="a,b","b,c"`, I think.

@PhyberApex a PR with the first steps would be great, thanks! If I remember right, the filtering code is pretty complex.