feat: Add Custom Errors to LiquidityManagerV2 #45
Conversation
This file contains hidden or 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
added 4 commits
September 9, 2025 12:45
SynnekOG
added
documentation
Neros0
approved these changes
Sep 9, 2025
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.
PR Description
Summary
This PR introduces custom Solidity errors to
LiquidityManagerV2.solfor more gas-efficient and descriptive error handling.Changes
LiquidityManager__PoolAlreadyInitializedLiquidityManager__PoolNotInitializedLiquidityManager__InvalidTokenAddressMotivation
Using custom errors instead of
requirewith strings:Notes
These custom errors will be integrated into core liquidity management logic in upcoming commits to replace generic
requirechecks.