Add support for FX pools #616
Closed
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
covered by syncAllPoolsFromSubgraph
covered by syncAllPoolsFromSubgraph
covered by syncAllPools
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 pull request adds:
support for FX pools by adding a parser for the subgraph data.
In the mapper I'm extracting the structure we had in the pool-creator-service and splitting it into two parts:
This helps with testing and adding updates, or upserts will be easier, since we have the clean data object.
I changed foreign keys constrains related to pools to allow for deleting a pool with all associated records.
added fishery for setting up object factories in tests