Skip to content

Register operations#621

Merged
jbaxleyiii merged 5 commits intovNEXTfrom
abernix/register-operations
Oct 8, 2018
Merged

Register operations#621
jbaxleyiii merged 5 commits intovNEXTfrom
abernix/register-operations

Conversation

@jbaxleyiii
Copy link
Copy Markdown
Contributor

This PR is opened on behalf of @abernix who is muscling through shipping the rest of this feature. It provides a new feature of the apollo platform to register operations which will be the only allowed operations that a server can execute.

more info coming soon about this feature 🔜

abernix and others added 5 commits October 4, 2018 12:50
This newly introduce command leans on the existing `queries:extract` logic.
Operations needs to be attached to a specific client
so this PR adds the ability to send a client name,
client id, and client version to annoate the manifest
of operations. This will make it much easier to validate
schema changes against registered queries and have
a sane governace strategy
A point of clarity, client identifier is a better term for a value
that can range from UUID, abritray strings, certs, and really
anything else. Client Id was leading to confusion about the generation
state and possible values (i.e. id's are typically a monotype)
this adds client identity to the registration step!
@jbaxleyiii jbaxleyiii merged commit c102025 into vNEXT Oct 8, 2018
@jbaxleyiii jbaxleyiii deleted the abernix/register-operations branch October 8, 2018 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants