mongo-graphql-starter

Query whitelisting

Change the behavior of _id fields that are set to nonNull(). Now that field on the input object will override and allow null.

This is in theory a breaking change, but in practice will just fail to error out in areas you probably didn't want an error to begin with, ie if you're creating an object and wanting Mongo to assign the _id value for you.

Version 1.0!

Breaking changes: non-queryable fields have a new (simpler) api.

New Features: non-null fields.

Upgrade dependencies

Dependency upgrades

Non-queryable properties

Update TypeScript generation dependencies

Fix bug with generated imports to resolver additions

schemaAdditions and resolverAdditions implemented, allowing for arbitrary graphql content independent of Mongo-based types

Bug fixes related to code generation

Fix https://github.com/arackaf/mongo-graphql-starter/issues/80

Tweak docs to clarify that esm usage won't work with Node's native esm.

Fix performance bug with many-many relationships.

No changes. README update only.

Prettier config tweak

Update graphql-tools, tweak prettier config

Array containsAll query added

Add fragment support

Add $lookup support to the aggregation pipeline. This allows for collection paging for relationship queries.

By default, the existing data loader lookup is used, unless paging is performed on the collection, in which case the necessary $lookup is added to the aggregation.

A global setting, as well as a query-specific PREFER_LOOKUP property can manually opt into it even when not needed.

Fix a bug that emitted invalid GraphQL when there were no types that were writable / not readonly.

Not in filter added.

Fixed a bug for mongoid arrays, where null values weren't handled properly.