[Frontend] Create-stream amount error message shows only when input is VALID (inverted logic)

[ogazboiz]

Telegram: https://t.me/+DOylgFv1jyJlNzM0

Why this matters

In frontend/src/app/streams/create/page.tsx, the inline amount error renders with:

{formData.amount && !validateAmountInput(formData.amount, TOKEN_DECIMALS) && (
  <p className="text-xs text-red-400">Amount must be greater than 0 with max {TOKEN_DECIMALS} decimals</p>
)}

validateAmountInput returns an error string when invalid and null when valid. So !validateAmountInput(...) is truthy exactly when the amount is valid — the red error appears for good input and disappears for bad input. The condition is inverted.

Acceptance criteria

• Render the error only when validateAmountInput(...) returns a non-null message, and display that message (instead of a generic hardcoded string)
• Manually verify: valid amount → no error; empty/zero/too-many-decimals → correct error text

Files to touch

• frontend/src/app/streams/create/page.tsx

Out of scope

• The wizard's amount step (separate component).

[Belzabeem]

@Belzabeem has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to fix this bug as I have experience correcting inverted validation logic in React forms and replacing hardcoded error strings with dynamic messages returned from validator functions. If given the opportunity, I am confident I can deliver the one-line fix to render the error only when validateAmountInput returns a non-null message, with manual verification confirming correct behaviour for all input states

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Belzabeem to this issue.

[dmystical-coder]

@dmystical-coder has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to work on this issue. Kindly assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dmystical-coder to this issue.

[drips-wave]

Congratulations, @dmystical-coder! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @dmystical-coder: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @dmystical-coder as part of the Stellar Wave Program's 5th Wave 🥳

😎 @dmystical-coder: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.