[Frontend] StreamCreationWizard shadows global 'timeout' with a state variable

[ogazboiz]

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

Why this matters

In frontend/src/components/stream-creation/StreamCreationWizard.tsx:

const [timeout, setTimeoutError] = useState(false);

Naming the state variable timeout shadows the global timeout/relatives and reads confusingly next to the setTimeout calls in the same component (startPolling uses setTimeout). The setter is even named setTimeoutError, implying the intended state name was timeoutError/isTimeout.

Acceptance criteria

• Rename the state variable to something like isTimeout/timeoutError (matching the setter)
• Update all references (the {timeout ? ... : ...} JSX branches)
• No behaviour change

Files to touch

• frontend/src/components/stream-creation/StreamCreationWizard.tsx

Out of scope

• The polling response-shape bug ([Frontend] Stream-creation confirmation polling never succeeds (wrong response shape + address) #502).

[somotochukwu-dev]

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

Good day maintainer,
Please assign this issue to me
Thanks.

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

[SharifIbrahimDev]

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

Hi @ogazboiz, I’d like to work on this issue.

I can refactor the StreamCreationWizard state naming to eliminate the timeout shadowing and improve readability without changing existing behavior. I’ll update the state variable to a clearer name such as timeoutError or isTimeout, adjust all related JSX references, and verify the polling flow continues to work correctly alongside the existing setTimeout usage.

I’ll also ensure the refactor remains clean, consistent, and fully backward-compatible.

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

[drips-wave]

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

🧑‍💻 @SharifIbrahimDev: 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 @SharifIbrahimDev as part of the Stellar Wave Program's 5th Wave 🥳

😎 @SharifIbrahimDev: 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.