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 fetch #575

Conversation

EverlastingBugstopper
Copy link
Contributor

@EverlastingBugstopper EverlastingBugstopper commented May 25, 2021

This refactor is in the same spirit as #557

I thought this would go quicker, took me about an hour or so to just refactor one command. Going to stop doing this refactor until I talk with Irina to make sure it's a good idea (I still think it is... the API is ssooo much cleaner, problem is that it's just a bit time consuming and I have other things to write up)

@EverlastingBugstopper EverlastingBugstopper changed the title wip: refactor subgraph check and add line numbers wip: refactor subgraph fetch May 25, 2021
@EverlastingBugstopper EverlastingBugstopper changed the title wip: refactor subgraph fetch chore: refactor subgraph fetch May 25, 2021
@EverlastingBugstopper EverlastingBugstopper force-pushed the avery/refactor-subgraph-check branch from 382b668 to 4003978 Compare June 11, 2021 21:28
@EverlastingBugstopper EverlastingBugstopper force-pushed the avery/refactor-subgraph-fetch branch 2 times, most recently from cd2513b to e747d78 Compare June 11, 2021 22:36
@EverlastingBugstopper EverlastingBugstopper force-pushed the avery/refactor-subgraph-check branch from 086980c to a7d9ce3 Compare June 23, 2021 15:16
@EverlastingBugstopper EverlastingBugstopper force-pushed the avery/refactor-subgraph-fetch branch from e747d78 to 3ab512b Compare June 23, 2021 15:19
@EverlastingBugstopper EverlastingBugstopper force-pushed the avery/refactor-subgraph-fetch branch from 3ab512b to 6eadfdd Compare June 23, 2021 15:22
@EverlastingBugstopper EverlastingBugstopper merged commit 0fabe0c into avery/refactor-subgraph-check Jun 23, 2021
@EverlastingBugstopper EverlastingBugstopper deleted the avery/refactor-subgraph-fetch branch June 23, 2021 15:23
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