Fix withdrawal functionality when TVL limit is reached #174
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.
Description
This PR addresses the issue where withdrawal functionality was incorrectly disabled when a strategy reached 100% of its TVL limit. The changes ensure that only deposits are disabled when the TVL limit is hit, while withdrawals remain functional.
Changes Made
strategies.atoms.ts
to separate deposit and withdrawal logic:depositsDisabled
property based on TVL limitwithdrawalsEnabled
to always be trueDeposit.tsx
component:depositsDisabled
propertyHow to Test
maxTVL
for a strategy instrategies.atoms.ts
to below its current TVL valueCloses #163