Releases: Khan/graphql-flow
Releases · Khan/graphql-flow
v1.0.0
Major Changes
-
1e1de13: BREAKING: Change config file format, split into 'crawl' and 'generate' sections
See schema.json for new organization. -
284be55: [breaking] remove support for running graphql-flow via jest
Now the cli tool is the only way to invoke graphql-flow.
-
9f7f2d1: Breaking: removed support for multiple config files (to be replaced with override support in the central config file)
Minor Changes
-
a99fc38: Support multiple 'generate' configs, allowing projects to have different settings for different directories or files
config.generate
can now be an object or an array of objects, withmatch
andexclude
arrays (either a RegExp or a string that will be passed tonew RegExp()
) to fine-tune which files they apply to.
Patch Changes
- bcc06d0: Use jsonschema for validating the config file
v0.3.0
Minor Changes
- 093fa5f: Enable
experimentalEnums
in a config or subconfig file in to enable the export of flow enum types, which replace the default string union literals. The type currently comes with eslint decorators to skirt a bug in eslint and flow. - 5078624: Users can add files with the name ending in
graphql-flow.config.js
with a subset of the config fields (options
,excludes
) in order to have more granular control of the behavior. Another field,extends
, takes the path of another config file to use as a base and extends/overrides fields. If noextends
is provided, the file completely overwrites any other config files (as far asoptions
andexcludes
).
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.1.0
Minor Changes
- b08ed1b: Build out a cli tool that does our own parsing of javascript files, dramatically speeding things up!