Skip to content

[GENERAL] Clean up dead and inconsistent frontend code paths #16

@EQuBitC18

Description

@EQuBitC18

Issue Type

Other

Description

Frontend contains legacy and duplicate artifacts that create confusion and maintenance overhead, including an unused service with stale imports/endpoints and overlapping component implementations.

Additional Context

For example:
Inspect src/Service/MicrocourseDataService.js.
Observe import from missing module ../http-common and request to /api/tutorials.
Compare component folder and observe duplicate patterns (ScrollProgressBar.tsx and scroll-progress-bar.tsx).

Frontend should have one clear implementation path per concern, no stale imports, and no dead service code pointing to nonexistent endpoints.

Known candidates are (if you can find more that's nice!):

Tezrisat_Frontend/tezrisat_frontend/src/Service/MicrocourseDataService.js
Tezrisat_Frontend/tezrisat_frontend/src/components/ScrollProgressBar.tsx
Tezrisat_Frontend/tezrisat_frontend/src/components/scroll-progress-bar.tsx

Find as many dead code as you can.

Priority: Low

Checklist

  • I have searched existing issues and discussions
  • This is not a security vulnerability (see SECURITY.md)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestgood first issueGood for newcomersquestionFurther information is requested

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions