This repository has been archived by the owner on Oct 11, 2021. It is now read-only.
Causality graphql connection using relay. #13
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
erikdstock
force-pushed
the
causality-gql
branch
2 times, most recently
from
df7bf6d to
299d104
Compare
erikdstock
force-pushed
the
causality-gql
branch
from
fbedfb0 to
2dd1c17
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Should be pretty close, but causality authorization headers need adjustment so we are in a holding pattern.
Has some new .env values. This also includes a relay setup since types on our auctions data would be a huge win.
If auth headers are not possible we could probably fetch this data on the server in the short term just to show the data - not ideal though.
relates to #3