Skip to content
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

chore: refactor subgraph publish #630

Conversation

EverlastingBugstopper
Copy link
Contributor

@EverlastingBugstopper EverlastingBugstopper commented Jun 23, 2021

Updates rover subgraph publish to conform to the new architecture.

TODO:

  • make sure it's ok that we send "" for the "revision" field on the publish mutation

@EverlastingBugstopper EverlastingBugstopper merged commit e124da5 into avery/refactor-subgraph-check Jun 25, 2021
@EverlastingBugstopper EverlastingBugstopper deleted the avery/refactor-subgraph-publish branch June 25, 2021 17:10
EverlastingBugstopper added a commit that referenced this pull request Jul 26, 2021
* chore: refactor subgraph check

This commit does a lot of heavy lifting for the pending rebase.

1) Creates new input and output types in rover-client for subgraph check
2) Moves GitContext out of rover::utils to rover-client::utils
3) Creates error code E029 for composition errors
4) Styles cloud-composition errors like harmonizer

* chore: refactor subgraph fetch (#575)

* chore: refactor subgraph publish (#630)

* chore: refactor config whoami (#633)

* chore: refactor subgraph delete (#639)

* chore: refactor subgraph list (#640)

* chore: refactor subgraph introspect (#641)

* chore: refactor graph introspect (#643)

* chore: refactor release update checker (#646)

* chore: begin adding shared types and consolidate check operations (#652)

* chore: move GraphRef to rover-client (#664)

* chore: refactor the rest of rover-client (#675)

* chore: do not re-export queries

* chore: finish wiring OperationCheck error

* chore: adds graphql linter (#677)

* fix: graph_ref -> graphref

* feat: structured output (#676)
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.

1 participant