v0.15.x to v0.16.x

Filter on Relations

In v0.16.x we made a big step forward in the functionality of relations by allowing for filtering on their properties. While making this change it was aso decided to unify the way that relations are defined.

In previous versions of nestjs-query you could define relations using the @Relation or @Connection decorator as well as manually defining them when creating your resolvers, this leads to an in consistent experience while using nestjs-query. In the latest version all relations MUST be defined using the decorators.

In v0.16.x there are two new decorators (@FilterableRelation, @FilterableConnection) exposed to allow you to decide if end users should be able to filter on the relation.

To read more about the new decorators as well as defining relations you can read the relations docs

Filter Definitions

In v0.16.x filters are defined based on the operation (read, update, delete). In previous versions of nestjs-query all filters for a type in graphql were the same. In v0.16.x this behavior needed to change in order to support filtering on relations.

This should be a passive change for most, however the generated graphql schema will contain new types for each filter operation.