|
1 | | -## master |
| 1 | +## 0.0.0-semantically-released |
2 | 2 |
|
3 | | -## 0.0.0-semantically-released (September 12, 2016) |
4 | | -This package publishing automated by [semantic-release](https://github.com/semantic-release/semantic-release). |
5 | | -[Changelog](https://github.com/nodkz/graphql-compose/releases) is generated automatically and can be found here: https://github.com/nodkz/graphql-compose/releases |
6 | | - |
7 | | -## 1.0.12 (September 6, 2016) |
8 | | -- fix: Resolvers now return mongoose documents. It's useful for your resolver wrappers. Now you have access to virtual fields, model methods via `source` or `source.record`. |
9 | | -- Update dependencies |
10 | | -- Update order of imported modules, due eslint warnings |
11 | | -- Flow 0.32 |
12 | | - |
13 | | -## 1.0.11 (September 5, 2016) |
14 | | -- Add support for `mongoose.Schema.Types.Mixed` type. Many thanks to @taion for his [graphql-type-json](https://github.com/taion/graphql-type-json) package. |
15 | | - |
16 | | -## 1.0.10 (August 25, 2016) |
17 | | -- Resolvers `findOne` and `findById` now by default return object with data, not mongoose document. |
18 | | - |
19 | | -## 1.0.9 (August 15, 2016) |
20 | | -- fix: babel build via the workaround https://phabricator.babeljs.io/T2877#78089 Huh, it's too tricky to use Map/Set in ES5. |
21 | | - |
22 | | -## 1.0.8 (August 13, 2016) |
23 | | -- fix: babel build process |
24 | | - |
25 | | -## 1.0.7 (August 10, 2016) |
26 | | -- Update packages, add `babel-plugin-transform-runtime` for build process. Fix [issue](https://github.com/nodkz/graphql-compose-connection/issues/2) for vanilla node.js users without babel (thanks @jacobbubu). |
27 | | - |
28 | | -## 1.0.6 (August 8, 2016) |
29 | | -- Fix `projection` extraction from `record` for `updateById` and `updateOne` resolvers. |
30 | | -- Intermediate types now passed to TypeStorage (Enums, SubSchemas) when converting mongoose models. |
31 | | - |
32 | | -## 1.0.5 (July 22, 2016) |
33 | | -- Added typeStorage. If you create resolver in second time, it should reuse existed internal types |
34 | | - |
35 | | -## 1.0.4 (July 20, 2016) |
36 | | -* Expose `fieldsConverter` methods |
37 | | -* Fix filterHelper: if `filter` InputType without fields, then do not add it to args |
38 | | -* Fix projectionHelper: make projection flat, before passing to mongoose |
39 | | -* Add `convertSchemaToGraphQL` method for creating cached graphql type from MongooseSchema |
40 | | - |
41 | | -## 1.0.3 (July 18, 2016) |
42 | | -* HotFix for connection resolver |
43 | | -* HotFix for operators' types in `filter` helper |
44 | | - |
45 | | -## 1.0.1 (July 18, 2016) |
46 | | -* Fix `peerDependencies` |
47 | | -* Update `flow` till 0.29 |
48 | | -* Other small fixes |
49 | | - |
50 | | -## 1.0.0 (July 15, 2016) |
51 | | -* Add connection resolver |
52 | | -* Add support for filtering with operators $gt, $gte, $lt, $lte, $ne, $in, $nin |
53 | | -* Small fixes |
54 | | - |
55 | | -## 0.0.6 (July 08, 2016) |
56 | | -* Rename `input` argument to `record` for mutations (due `graphql-compose-relay` compatibility). |
57 | | -`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. |
58 | | - |
59 | | -## 0.0.5 (July 07, 2016) |
60 | | -* Refactor Resolvers due changes in graphql-compose api |
61 | | -* Exports flow annotations |
62 | | - |
63 | | -## 0.0.3 (July 01, 2016) |
64 | | -* First beta version |
65 | | - |
66 | | -## 0.0.1 (June 07, 2016) |
67 | | -* Initial commit |
| 3 | +This package publishing automated by [semantic-release](https://github.com/semantic-release/semantic-release). Changelog is generated automatically and can be found here: https://github.com/graphql-compose/graphql-compose-mongoose/releases |
0 commit comments