Releases: aerogear/graphback
0.11.0-rc6
Merge pull request #870 from aerogear/renovate/babel-monorepo Update dependency babel-eslint to v10.1.0
0.11.0-rc5
fix: version format
0.11.0-rc4
Merge pull request #824 from aerogear/package-bumps fix: bump graphql-serve
0.11.0-rc3
chore: 0.11.0-rc3 (#786)
0.11.0-rc2
An early version of v0.11.0.
- Bug fixes
0.11.0-rc1
An early version of the 0.11.0.
Limitations:
- Limited database mapping capabilities
- No support for db relationships
Release blog post: https://medium.com/@wtr/graphback-plugin-based-realtime-database-generator-78f4f608b81e
0.10.2
graphql-migrations
It's now possible to create database relationships from the 1:M
side of your data model!
type User {
id: ID!
messages: [Message]
}
This creates a userId
foreign key column in the message
table.
0.10.1
Graphback-Codegen-Client
- Generate relationship variables in mutations, fragment, subscriptions, queries.
0.10.0
BREAKING changes for CLI/ and runtime.
Graphback-CLI
- Removed
init
method
Init method is no longer available. To start new boilerplate project
please use graphql-cli init
command instead that now incorporates Graphback.
Graphback
- Added runtime layer
Runtime layer gives developers ability to run GraphQL server basing on input model
without code generation. All resolvers are created at runtime giving developers ability to update applications
on the fly. For more information please check official documentation for runtime layer.
- Deprecating graphback as way to interact with the Graphback ecosystem
Graphback package offers multiple helpers however to fully configure all generators and other capabilities
developers can use individual packages:
@graphback/codegen-client
@graphback/codegen-resolvers
@graphback/codegen-schema
@graphback/core
@graphback/runtime
graphql-migrations
GraphQL-Migrations
-
Added a new library
graphql-migrations
for executing database migrations. -
migrateDB
directly compares the input model with the current database and uses the generated diff to update the database structure. This mode does not generate any migration metadata. -
migrateDBUsingSchema
updates the database by comparing the input model with the previous model. This mode generates migration metadata which is persisted to the local filesystem and to the database.
0.10.0-rc3
Merge pull request #583 from aerogear/0.10.0-rc3 0.10.0-rc3