fix(weavedrive): use fetch in lieu of arweave js client to make graphql calls. Fix graphql operations. #382
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.
This PR fixes an issue in WeaveDrive, where a non-existent arweavejs client was being used to call an arweave gateway. The rest of the impl uses an internal api built around
fetch
, so I simply swapped the use arweavejs to using that api as well.This PR also fixes malformed graphql queries that would fail, if made to an arweave gateway.
This PR also fixes a bug where module tags were being checked instead of process tags, when determining the
Availablity-Type
Finally, I added tests to assert the correctness of loading txs in
Availability-Types
Assignments
andIndividual