-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reject subgraphs with invalid @derivedFrom fields #1213
Comments
lutter
added a commit
that referenced
this issue
Sep 28, 2019
These validations follow the corresponding validations in graph-cli, and make sure users do not deploy invalid subgraphs, e.g., because they have not updated their subgraph or graph-cli Fixes #1213
lutter
added a commit
that referenced
this issue
Oct 1, 2019
These validations follow the corresponding validations in graph-cli, and make sure users do not deploy invalid subgraphs, e.g., because they have not updated their subgraph or graph-cli Fixes #1213
lutter
added a commit
that referenced
this issue
Oct 1, 2019
These validations follow the corresponding validations in graph-cli, and make sure users do not deploy invalid subgraphs, e.g., because they have not updated their subgraph or graph-cli Fixes #1213
leoyvens
pushed a commit
that referenced
this issue
Oct 2, 2019
These validations follow the corresponding validations in graph-cli, and make sure users do not deploy invalid subgraphs, e.g., because they have not updated their subgraph or graph-cli Fixes #1213
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Graph CLI, since this commit disallows a number of errors around the
@derivedFrom
annotation. It is still possible to deploy such subgraphs tograph-node
, e.g., by using an older version ofgraph-cli
. The issues thatgraph-cli
flags will become serious issues with the relational schema, andgraph-node
should reject new deployments of subgraphs with these problemsThe text was updated successfully, but these errors were encountered: