Skip to content

fix(stream-detail): un-dead-code the high-fee warning (FlowwStar/FlowStar#366)#400

Open
jdjioe5-cpu wants to merge 1 commit into
FlowwStar:mainfrom
jdjioe5-cpu:fix/issue-366-is-high-fee-dead-code
Open

fix(stream-detail): un-dead-code the high-fee warning (FlowwStar/FlowStar#366)#400
jdjioe5-cpu wants to merge 1 commit into
FlowwStar:mainfrom
jdjioe5-cpu:fix/issue-366-is-high-fee-dead-code

Conversation

@jdjioe5-cpu

Copy link
Copy Markdown

Closes #366. withdrawFeeHigh/cancelFeeHigh were always-false (compared estimatedFee to itself via TYPICAL_FEES.X.typical). Pass TYPICAL_FEES.X.typical / 2 as the reference so isHighFee's fee > avg*2 shape holds.

Closes FlowwStar#366.

In app/app/stream/[id]/page.tsx, both withdrawFeeHigh and cancelFeeHigh
passed (estimatedFee, TYPICAL_FEES.X.typical) where estimatedFee IS
TYPICAL_FEES.X.typical — so `isHighFee(fee, fee)` always returned false
(fee > fee*2 never holds).

Pass TYPICAL_FEES.X.typical / 2 as the second arg so that
isHighFee(estimatedFee, baseline) = (estimatedFee > baseline * 2) holds
the intended shape. Add a comment explaining the workaround until a real
network fee estimate can be plumbed in (a separate change out of scope
here).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

good first issue: fix unreachable 'high fee' warning in stream detail page — isHighFee compares a value to itself

1 participant