Co-authored-by: Jason Kuhrt <jasonkuhrt@me.com>
COMPLETES INITIAL DEVELOPMENT
BREAKING CHANGE:
You will now need to install Nexus Schema from the npm package `nexus` instead of `@nexus/schema`.
closes#582
As discussed. In most cases resolver shorthands are not a serious use of the API.
BREAKING CHANGE:
Resolver shorthand API is now removed. The following will now not typecheck:
```ts
t.string('foo', () => ... )
```
Instead use:
```ts
t.string('foo', { resolve: () => ... })
```
Runtime support is still intact but will result in a logged warning. Runtime support will be removed in the next Nexus release.
closes#410
BREAKING CHANGE:
The graphql peer dep requirement has been bumped to v15.
No graphql v15 exclusive features have been shipped yet. But this update
sets us up to begin that work.
Support for graphql v14 and lower has been dropped. It may technically work
still (the test suite did not show any major reasons why it won't, for
now/currently) but there is no guarantee about that remaining so in the
future. Internally we are only testing against v15. Certain new grpahqljs
v15 features like interfaces being able to implement other interfaces will
be released in the future.
If you absolutely cannot upgrade from graphql v14 right now then stay with
@nexus/schema v15. But if you also really need a new @nexus/schema feature
on v16+ (future) then you can try your luck with it an older version of
graphqljs.
* Update CI config to test examples
* Fix star wars example
* Update yarn.lock of nexus-prisma example
* Fix kitchen-sink example
* Update nexus to beta9 in star wars example
* Upgrade nexus in ts-ast-reader example
* Fix ghost example
* Fix githunt-api example
* Make githunt-api test pass
* Fix nexus-prisma example
* Fix typing in ts-ast-reader
* Use yarn link when nexus deps is already 0.12.0-beta.9
* Remove yarn link from example_ghost
* Make sure generated files are up to date
Tim Griesser
Jason Kuhrt
Flavian Desverne
Jason Kuhrt
Bjorn Lu
Brice BERNARD