Creates a fully functioning, performant, extensible GraphQL endpoint from a Mongo DB. Supports middleware, Mongo 4 transactions.
MIT License
Query whitelisting
Published by arackaf about 2 years ago
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.
Published by arackaf over 2 years ago
Version 1.0!
Breaking changes: non-queryable fields have a new (simpler) api.
New Features: non-null fields.
Published by arackaf over 2 years ago
Upgrade dependencies
Published by arackaf over 2 years ago
Dependency upgrades
Published by arackaf over 2 years ago
Non-queryable properties
Published by arackaf over 3 years ago
Update TypeScript generation dependencies
Published by arackaf over 3 years ago
Fix bug with generated imports to resolver additions
Published by arackaf over 3 years ago
schemaAdditions and resolverAdditions implemented, allowing for arbitrary graphql content independent of Mongo-based types
Published by arackaf over 3 years ago
Bug fixes related to code generation
Published by arackaf over 3 years ago
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.
Published by arackaf over 3 years ago
Fix performance bug with many-many relationships.
Published by arackaf over 3 years ago
No changes. README update only.
Published by arackaf over 4 years ago
Prettier config tweak
Published by arackaf over 4 years ago
Update graphql-tools, tweak prettier config
Published by arackaf over 4 years ago
Array containsAll query added
Published by arackaf almost 5 years ago
Add fragment support
Published by arackaf almost 5 years ago
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.
Published by arackaf about 5 years ago
Fix a bug that emitted invalid GraphQL when there were no types that were writable / not readonly.
Published by arackaf about 5 years ago
Not in filter added.
Fixed a bug for mongoid arrays, where null values weren't handled properly.