Closed vincentwschau closed 2 weeks ago
The changes in this pull request involve updates to the vault-controller
test suite and the VaultController
class within the megavault
API. A new test case has been added to handle scenarios with multiple vault subaccounts, including one invalid entry. Additionally, the getVaultMapping
function has been modified to return a filtered mapping of valid vaults, ensuring only those linked to valid perpetual markets are included. This enhances data integrity while maintaining existing method signatures and control flow.
File | Change Summary |
---|---|
indexer/services/comlink/__tests__/controllers/api/v4/vault-controller.test.ts |
Updated test case to handle three vault subaccounts, including one invalid. Renamed test case for clarity. |
indexer/services/comlink/src/controllers/api/v4/vault-controller.ts |
Modified getVaultMapping function to return filtered validVaultMapping instead of vaultMapping , ensuring only valid entries are included. |
🐇 In the vaults where treasures lay,
A rabbit hops and starts to play.
With tests that check both strong and weak,
Valid paths are what we seek.
A mapping clear, no room for doubt,
In this code, we dance about! 🌟
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
@Mergifyio backport release/indexer/v7.x
backport release/indexer/v7.x
Changelist
Had a typo when returning valid/invalid vaults. Updated a test to catch this.
Test Plan
Unit test.
Author/Reviewer Checklist
state-breaking
label.indexer-postgres-breaking
label.PrepareProposal
orProcessProposal
, manually add the labelproposal-breaking
.feature:[feature-name]
.backport/[branch-name]
.refactor
,chore
,bug
.Summary by CodeRabbit
New Features
Bug Fixes
Tests