Skip to content

Restructure apollo queries:extract logic and manifest format.#611

Merged
abernix merged 8 commits intovNEXTfrom
abernix/relocate-common-tasks
Oct 8, 2018
Merged

Restructure apollo queries:extract logic and manifest format.#611
abernix merged 8 commits intovNEXTfrom
abernix/relocate-common-tasks

Conversation

@abernix
Copy link
Copy Markdown
Member

@abernix abernix commented Oct 2, 2018

Breaking changes: This changes the output format of the manifest generated by queries:extract to be in a more evolvable format. Existing users of the manifest produced by manifest.json should take care to observe the new manifest format, as indicated by the top-level presence of a version attribute (now 1, previously undefined).

In general, this just moves some bits of often repeated portions of the CLI into a unified location where they can be shared by more modules as we use more and more portions in multiple places.

As these commands continue to grow, it seems to make sense to also move
their logic into a common tasks library.
…ations.

While these assertions made less sense when every task was in the same file,
a more composable approach to tasks begs for some general assertions to the
context (`ctx`) that's being used.
I'm pretty sure there's a lot more to life than being really, really async.
@abernix abernix requested a review from jbaxleyiii October 2, 2018 13:50
Copy link
Copy Markdown
Contributor

@jbaxleyiii jbaxleyiii left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@trevor-scheer wanted to flag you on this one as it starts the breaking changes for 3.0 line and will need to be rebased into your work

This will allow the manifest to be more resilient against future changes by
ensuring that the `version` is the most important attribute of its top-most
level.

Additionally, this includes the calculation of the signature which is used
by Apollo Engine, in order to match operations up with each other.
@abernix abernix force-pushed the abernix/relocate-common-tasks branch from 0869789 to b254b3d Compare October 2, 2018 14:31
@abernix
Copy link
Copy Markdown
Member Author

abernix commented Oct 2, 2018

@trevor-scheer Happy to assist/adjust if this breaks anything you currently have in-flight.

While I'm at breaking changes, we don't have a compelling enough reason to
support SHA-512 just yet.  The ask for 512 was previously my own since it
could have a longer lifespan (and is sometimes faster) and the base64
encoding was to reduce the rather long length of SHA-512's hex encoding
(which is 128-bytes rather than the 64-bytes which result from SHA-256's
hex encoding).
@trevor-scheer
Copy link
Copy Markdown
Contributor

@abernix @jbaxleyiii nothing in flight that would be affected AFAIK, taking a look now to be sure. Thanks for the heads up!

@abernix abernix changed the base branch from master to vNEXT October 8, 2018 18:27
@abernix abernix merged commit ced4cc6 into vNEXT Oct 8, 2018
@JakeDawkins JakeDawkins deleted the abernix/relocate-common-tasks branch January 22, 2019 19:12
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.

3 participants