Alexander Tømmerås

The `camel_case` was added to solve this issue btw: https://github.com/flugger/laravel-responder/issues/85

I like this idea. The data could be filtered before the transformation takes place, but sometimes you may want to filter based on relationships or fields calculated in a transformer....

Just so I'm understanding this correctly; if this happens before the transformation takes place, how would this differ from just filtering the data before sending it to the responder?

Makes sense, thanks! I've been wanting some functionality for filtering and ordering the data automatically using query string parameters in the past. I know it's not exactly what you're asking...

Haha, great. I'm not sure yet to be honest, but I believe a dedicated `Filter`concept or similar might make sense for this. Just throwing some ideas in the air, but...

Thinking about it some more and looking at some other packages handling similar things (https://github.com/spatie/laravel-query-builder, https://github.com/cerbero90/query-filters), I believe this should be handled more generally. Filtering, ordering and searching is so...

I'm trying to decide how to best handle query string parameters. The format I mentioned above... ``` ?filter[outdated]=true&sort=name ``` ...is basically based on the [JSON API spec](http://jsonapi.org/recommendations/#filtering). While this format...

> Seems a good addition to the package and it actually covers almost everything, it's actually even more than what I expected xD Great! > I'm not sure about which...

Excellent! We're eagerly waiting for this update, when do you think it could be released @developit ?

Any progress on this @travi ? Let us know if there's anything the community can help out with, I'd be happy to be of assistance.