feat(epic): 0.12.0 Plugin System and Internal Refactor

[tgriesser]

Summary of all changes in 0.12.0:

• Adds comprehensive "Plugins" API, see the docs for more info on what all these can help accomplish
• deletes previous types file before writing next (fix(typegen): delete prev file before writing next #252)
  • This helps VSCode pick up its changed version when types are updated
• Adds shouldExitAfterGenerateArtifacts to makeSchema config
  • Makes it possible to exit after the types are generated, useful if you do not check a schema artifact into source control, but wish to generate before the code runs.

Plugins:

• Add nullabilityGuardPlugin, to help provide fallback values when null is returned in a non-null field position. See the docs for more info.
• Add fieldAuthorizePlugin. See the docs for more info
  • This is the same behavior as the (currently undocumented) behavior of having authorize on the field, but implemented more flexibly as a plugin. This will be automatically added if no plugins are specified, otherwise it will need to be imported & added to makeSchema alongside other plugins.

Breaking:

• Bumps the default minimum peer-dependency version of graphql-js to 14.5.0
  • Nexus uses the new extensions property on types to store metadata provided to Nexus types, in order to make them usable by plugins.
• Moves field level authorization to a Nexus plugin. This will automatically be enabled in the same way as the current behavior, so as to prevent breaking changes.
• Removes nexusWrappedType
  • This was an internal implementation detail which should not affect end users
• Removes t.modifyType API
  • This may not have ever worked, it was only intended to modify fields on an objectType which were originally implemented by an interface. Please open an issue if this is a breaking change for you, so we can understand the use-case and design a better API.

Additional

• Improves code coverage, adds base threshold to new PRs
• Warn on missing outputs in makeSchema config

[jasonkuhrt]

Relates to #98

[jasonkuhrt]

Great work, I understand but some subset of it :) Hope the feedback is useful!

[beeplin]

I noticed that nexus-prisma 0.5.0 is out as a nexus plugin. Does that mean this plugin system is ready to use now for, say, auth usage, too?

[jasonkuhrt]

Hey @beeplin, only the typedef aspect is pluggable right now. And it is very early. But yes available in the latest beta. The available part does not have middleware yet, so does not help with auth. The nexus plugin features in beta now came from #236 which is a conceptual subset of this PR.

[larsivi]

I want to use the plugin system in conjunction with prisma 1 and nexus-prisma (the old one), since Prisma 2 and friends are currently not an option. nexus-prisma 0.3.8 does use nexusWrappedType however (see graphql-nexus/nexus-plugin-prisma#520).

Is there some easy way to migrate nexusWrappedType to a public API?