[Frontend] tsconfig.json — enable noImplicitReturns and noFallthroughCasesInSwitch

[ogazboiz]

Join the discussion on Telegram

Why this matters

Two cheap strictness wins missing from frontend/tsconfig.json:

• noImplicitReturns: true — catches functions where some paths return and others don't (e.g. the various switch statements in useStreamEvents, dashboard-view's renderContent which currently relies on a trailing return)
• noFallthroughCasesInSwitch: true — catches the next missing break before it ships

Both are documented as recommended in the same \"// Style Options\" block of backend/tsconfig.json (currently commented out there too — could be a follow-up for backend).

Acceptance criteria

• Add both flags to frontend/tsconfig.json
• Fix anything the checker surfaces
• npm run build passes

Files to touch

• frontend/tsconfig.json

Out of scope

• Backend tsconfig tightening (separate issue if wanted)

[Thoni76]

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

I’m a smart contract and full-stack developer who turns complex ideas into secure, production-ready blockchain code.
With strong skills in Rust and Solidity, I build systems that are fast, safe, and built to last.
My experience with the Stellar SDK lets me ship real-world Web3 solutions that actually move value

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

[midexol]

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

Hi maintainer I would like to work on this issue please assign it

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

[khanavi272-spec]

@khanavi272-spec 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

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

[extolkom]

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

Please assign me

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

[drips-wave]

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

🧑‍💻 @extolkom: 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 🌊