feat(LiquidityManagerV2): add mappings for pools, positions, and tokens #53
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.
PR Description
Summary
Introduces new mapping structures to
LiquidityManagerV2for improved pool management, user tracking, and token support.What's Changed
poolInfo→ store pool details by token pairuserPositions→ track liquidity positions per usersupportedTokens→ define which tokens can be used in liquidity provisionpoolKeys→ simplify access to pool identifierstokenPairToPoolId→ map token pairs to pool IDsforge fmtfor consistent formattingWhy
Impact
LiquidityManagerV2functionality.