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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: fee issue utilizing fee hook #1679
fix: fee issue utilizing fee hook #1679
Changes from 1 commit
cae5351
6b58042
a24f3e8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codebase verification
Based on the search results, I can now generate the final response:
Inconsistent Balance type handling detected in fee estimation
The codebase shows inconsistent handling of partial fees, where some components properly create Balance types while others directly use the raw partial fee:
governance/post/castVote/Cast.tsx
governance/delegate/modify/ModifyDelegate.tsx
governance/delegate/remove/RemoveDelegate.tsx
staking/solo/stake/index.tsx
sendFund/InputPage.tsx
staking/solo/tuneUp/index.tsx
crowdloans/contribute/Contribute.tsx
Consider applying the same type safety pattern
api?.createType('Balance', partialFee)
consistently across all fee estimations.🔗 Analysis chain
LGTM! Type safety improvement for fee estimation.
The changes properly ensure type safety by creating a Balance type from the partial fee. This is a good practice as it maintains consistent typing throughout the application.
Let's verify the Balance type usage across the codebase:
Also applies to: 232-232
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 6232
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Critical: Fee estimation parameters need revision
The current implementation has potential issues:
['1', undefined]
may not accurately reflect the actual transaction parametersConsider updating the implementation to:
Also, add error handling: