Duplicate EnrollmentStatus and QuizResult type definitions cause compilation errors

[DeFiVC]

What

Two type definition files have duplicate identifiers that will cause TypeScript compilation errors:

1. src/types/course.ts: EnrollmentStatus is defined twice — line 30 ("not_enrolled" | "active" | "completed" | "dropped") and line 98 ("not_enrolled" | "enrolled" | "in_progress" | "completed" | "expired"). The second silently shadows the first. Additionally, CourseEnrollment declares status twice (required on line 30, optional on line 47).

2. src/types/quiz.ts: QuizResult is defined as an interface on line 64 and then redefined as export type QuizResult = QuizAttempt on line 98. This is a duplicate identifier error.

Why

TypeScript will either refuse to compile or produce unpredictable type behavior. Any code depending on EnrollmentStatus union members or importing QuizResult will break. The duplicate status property in CourseEnrollment creates undefined required/optional semantics.

Scope

• Pick a single authoritative EnrollmentStatus definition in src/types/course.ts
• Remove the duplicate status property from CourseEnrollment
• Either remove the QuizResult interface or the type alias in src/types/quiz.ts
• Update any consumers that depend on the removed/changed types

Acceptance criteria

• No duplicate type definitions in course.ts or quiz.ts
• EnrollmentStatus has a single, correct definition
• CourseEnrollment.status appears once (with correct required/optional semantics)
• QuizResult has a single definition
• All files importing these types still compile
• submitQuiz return type matches actual API response

Technical context

• Files: src/types/course.ts:30,47,98, src/types/quiz.ts:64,98
• Consumer: src/lib/api/courses.ts
• Consumer: src/lib/api/quizzes.ts
• Consumer: src/lib/hooks/use-courses.ts

[ranjeet150]

Hi maintainers,

I would like to resolve this issue. Here is my proposed execution plan:

• Implementation: Implement Duplicate EnrollmentStatus and QuizResult type definitions cause compilation errors following the existing UI design system, accessibility standards, and responsive styling.
• Testing: Add component unit tests verifying user interactions and rendering states.

I am ready to start immediately—please feel free to assign this to me!

[codemagician1949]

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

please can i hop on this, promise to make all ci passes and run a thorough e2e test

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

[drips-wave]

Congratulations, @codemagician1949! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@codemagician1949's PR #470 was approved and merged by @DeFiVC.

🏆 @codemagician1949: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,465 total points). Track your full progress on GrantFox.

👏 Great work, @codemagician1949! Keep contributing to ChainLearnOfficial.

[drips-wave]

This issue has been completed by @codemagician1949 as part of the Stellar Wave Program's 9th Wave 🥳

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