Mathias Polligkeit

There should be an option to silently ignore invalid parameters instead of returning changeset errors.

- [ ] Implement the remaining operators for compound fields: `:==`, `:!=`, `:`, `:in` - [ ] Use concatenated field value instead of applying filter one-by-one.

Dynamic/Fragments

4

- [ ] #127 - [ ] support ordering by aggregates - [ ] support fragments when filtering? - [ ] support filtering by aggregates?

Default filter operators

2

Support passing filters as a keyword list or map without the need to specify an operator. ```elixir params = %{filters: %{title: "Psycho"}} Flop.validate_and_run(Movie, params, for: Movie) ``` The default operator...

We should add warnings - if path parameters or query parameters are missing in api documentation

Define best practices for defining api docs centrally

1

Currently, all the api doc macros are meant to be used within the controllers. It might be better if some definitions (i.e. shared parameters, warnings etc.) would be defined in...

Path, query and body params should be handled better. * Define shared parameters globally. * Support API Blueprint [attributes section](https://apiblueprint.org/documentation/specification.html#def-attributes-section) * Support Swagger [schema object](https://swagger.io/specification/#schema-object-80) * Support Swagger [parameters definition...

Right now, BlueBird doesn't support api versioning. Everything is put into one single documentation. However, a version must be specified in Swagger. I suggest to gradually add support for api...