Clean up unused variables and parameters#261
Merged
Conversation
turbolent
force-pushed
the
bastian/clean-up
branch
from
dbdd114 to
247337f
Compare
6 tasks
jribbink
approved these changes
Apr 14, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Prepare for #223
Used the linter to find unused variables and parameters.
There are several unused variables in the tests, results of calls to
getBalanceandgetYieldVaultBalance– can these actually be deleted if the result is unused, or are they asserting the balance can be get?For contributor use:
masterbranchFiles changedin the Github PR explorer