Duplicate routing sources (App and AppRoutes) create regression risk

[Mkalbani]

Problem

Routes are defined in two places with different path sets, but only one is mounted, making updates error-prone.

Evidence

• src/App.tsx
• src/routes/AppRoutes.tsx
• src/main.tsx

Scope

Frontend-only. No API needed.

Contributor Task

• Consolidate routing into one source of truth.
• Remove or deprecate the unused route map.

Done When

• Only one route definition source is used in runtime.
• Navbar and page routes are derived from the same route set.

[DeveloperEmmy]

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

I’d like to work on this because consistent routing reduces regressions; I have experience structuring React apps with single source-of-truth navigation.

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

[wokedi]

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

Hello maintainer, can you assign me this please? ETA: 8hours

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

[drips-wave]

Congratulations, @DeveloperEmmy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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

[Qoder-Undefined]

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

Hi maintainer am a full stack developer with experience in different languages I have carefully read this issue requirements and am confident in my skills to achieve it kindly assign ETA 2 hours

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

[Nacho1499]

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

Hello maintainer. am Nacho. a full-stack developer.
I would like to work on issue : “Duplicate routing sources (App and AppRoutes) create regression risk”.

This issue aligns well with my frontend architecture experience, especially organizing scalable routing systems and reducing maintenance complexity in React applications.

Why I am a good fit for this issue:

• I have experience refactoring routing structures into centralized and maintainable configurations.
• I understand the risks caused by duplicated route definitions and inconsistent navigation sources.
• I can consolidate route logic cleanly while preserving existing navigation behavior.
• I focus on improving maintainability, scalability, and reducing regression risk in frontend systems.
• I pay attention to keeping route-driven UI components synchronized with application navigation state.

My implementation approach would include:

• Auditing the current routing setup across App.tsx, AppRoutes.tsx, and main.tsx
• Consolidating all routes into a single source of truth
• Removing or safely deprecating unused route definitions
• Ensuring navbar navigation and rendered routes derive from the same configuration
• Verifying route consistency across navigation flows and direct URL access
• Keeping the refactor clean, minimal, and aligned with existing project structure

I will also ensure the final routing structure is easier to maintain, reduces future regression risk, and improves developer experience for future updates.

I would be excited to contribute this improvement. Thank you for considering my application.

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