You can download the latest Framework version by running npm install -g graphcool@next.
See the Forum for more information on the Framework Preview.
- A new local development workflow for functions is available. Additionally, there is a new & improved function runtime when deploying a service to a remote cluster, as well as in the local
graphcool-devenvironment. - You can now add templates to the service definition with a new add-template command.
- The initial project structure after upgrading a project to the Framework has been changed.
- Added GRAPHCOOL_PLATFORM_TOKEN env var.
- Removed the env command. From now on
.graphcoolrcis used to control deploy targets. - The CLI now can be run with node 6+.
- The CLI now reauthenticates if an invalid session is found.
- Service aliases with dashes are now supported in the CLI.
- Fixed a problem with the confirmation when deleting projects.
See the Forum for more information on the Framework Preview.
Note: You can get the latest Framework version by running
npm install -g graphcool@next.
- graphcool init does not deploy the service anymore.
- Improved usage texts in general and for delete.
- Added divider for project list.
- Improved output for written files.
- Allow .graphcool file in current folder.
- Search project configuration in parent folders.
- Deleting projects now asks for configuration in all cases.
- Introduced a shorthand notation for function code handlers.
- Renamed get-root-tokens to root-tokens.
- Added basic account command.
Currently, permission queries can't contain a header section, which will be changed soon. More information here.
Valid function names only use up to 64 alphanumeric letters, dashes and underscores. This is only checked when creating a new or updating an existing function and does not affect existing functions before updating them.
- Renamed Permanent Authentication Tokens (PATs) to Root Tokens.
- Renaming relations requires usage of @rename directive with oldName parameter.
- Schema Extensions are renamed to Resolvers.
- The system fields createdAt and updatedAt are now optional.
- The payload type of a resolver is now taken into account when validating the payload. This applies to required payload types as well as list payload types.
- Fixed a bug that affected subscription queries using variables of type ID.
- Fixed a bug that prevented default values from being deleted.
- Fixed a bug when changing a unique Int field to a unique String field.
- Fixed several issues when migrating float fields.
- Fixed a bug where using an invalid type in a resolver schema resulted in an internal server error.
- Fixed a bug that prevented scalar list input fields for resolvers.
- Fixed a bug when returning null for a string in a resolver.
- Fixed a bug when creating two types of same name a resolver.
See the Forum for more information on the Framework Preview.
Note: The latest CLI version of the Framework Preview is currently available in version 1.4. This will soon be corrected to version 0.4 instead.
- Wildcard permissions have been introduced that can be used to match all operations. The project configuration of a new project created with the CLI includes the wildcard permission by default.
- Added support for Modules in the project configuration.
- Environment variables can now be used for Graphcool Functions using the CLI.
- Added Root Token support in project configuration.
- Projects will not receive default public permissions for new fields/models.
- When deploying, subscription queries are now validated first. Also see here.
- User and File system types not included by default in projects created with the CLI.
- The module command has been renamed to modules.
- The --version command is now available.
- Changes for diff and deploy are now better grouped.
- Fixed a bug for displaying 504 and 502 error messages and other errors.
- Fixed a bug that caused unnecessary updates to scalar list fields when deploying.
- Fixed a bug that caused deploys to not being aborted when errors occured.
- Fixed a bug with the diff command for breaking changes.
- Fixed a bug when renaming a type with relations and deploying.