Releases: graphql-compose/graphql-compose-mongoose
Releases · graphql-compose/graphql-compose-mongoose
1.0.9 (August 15, 2016)
- fix: babel build via the workaround https://phabricator.babeljs.io/T2877#78089 Huh, it's too tricky to use Map/Set in ES5.
1.0.8 (August 13, 2016)
- fix: babel build process
1.0.7 (August 10, 2016)
- Update packages, add
babel-plugin-transform-runtime
for build process. Fix issue for vanilla node.js users without babel (thanks @jacobbubu).
1.0.6 (August 8, 2016)
- Fix
projection
extraction fromrecord
forupdateById
andupdateOne
resolvers. - Intermediate types now passed to TypeStorage (Enums, SubSchemas) when converting mongoose models.
1.0.5 (July 22, 2016)
1.0.5 (July 22, 2016)
- Added typeStorage. If you create resolver on the second time, it should reuse existed internal types
1.0.4 (July 20, 2016)
- expose
fieldsConverter
methods - fix filterHelper: if
filter
InputType without fields, then do not add it to args - fix projectionHelper: make projection flat, before passing to mongoose
- add
convertSchemaToGraphQL
method for creating cached graphql type from MongooseSchema
1.0.3 (July 18, 2016)
- HotFix for connection resolver
- HotFix for operators' types in
filter
helper
1.0.1 (July 18, 2016)
- Fix
peerDependencies
- Update
flow
till 0.29 - Other small fixes
1.0.0 (July 15, 2016)
Production ready release.
What's new:
- add connection resolver
- add support for filtering with operators $gt, $gte, $lt, $lte, $ne, $in, $nin
- small fixes
0.0.6 (July 08, 2016)
- rename
input
argument torecord
for mutations (duegraphql-compose-relay
compatibility).
Argument name input
is a reserved name for mutations' arg in Relay, and may contains not only document/record data (eg. clientMutationId, sort and filter args). So better solution for graphql-compose-mongoose
do not use this name, cause graphql-compose-relay
get all args from mongoose resolvers and put them to input
arg.