Fix lint errors

[rohitpaulk]

Summary by CodeRabbit

• Type Safety Improvements

  • Enhanced type annotations in various components
  • Added explicit type imports for models like RepositoryModel, BadgeAwardModel, and ConceptEngagementModel

• Code Cleanup

  • Removed TypeScript error suppression comments
  • Deleted unnecessary comments in template files

These changes primarily focus on improving type safety and code clarity across multiple components without altering core functionality.

[coderabbitai]

Walkthrough

This pull request focuses on enhancing type safety across multiple TypeScript components in the CodeCrafters frontend application. The changes primarily involve adding explicit type imports and annotations to various components, including badge cards, concept cards, track leaderboard, and track-related components. The modifications aim to improve type checking and reduce potential runtime errors by using more precise type definitions from imported models.

Changes

File	Change Summary
app/components/badges-page/badge-card.ts	Added BadgeAwardModel type import, explicitly typed badgeAward parameter in currentUserBadgeAwards getter
app/components/concepts-page/concept-card.ts	Imported ConceptEngagementModel, typed engagement parameter in latestConceptEngagement getter
app/components/header/account-dropdown.hbs	Removed TypeScript error expectation comments
app/components/referrals-page/referral-links-container.hbs	Removed TypeScript integration error comment
app/components/track-leaderboard.ts	Added RepositoryModel type import, explicitly typed currentUser.repositories and completedStagesCount
app/components/track-page/resume-track-button.ts	Imported RepositoryModel, explicitly typed filtered repositories
app/components/tracks-page/track-card.ts	Added RepositoryModel type import, explicitly typed repository in completedStagesCount getter
app/controllers/catalog.ts	Removed TypeScript error suppression comments for at(-1) method usage

Possibly related PRs

• dark mode for course page [1/2] #2013: Dark mode implementation for course page
• course dark mode #2024: Dark mode styling for various components
• Add dark mode toggle #2039: Dark mode toggle feature addition

Poem

🐰 Type safety, oh so neat!
Rabbits hop with code so sweet
Imports dancing, errors flee
TypeScript magic sets us free
Debugging becomes a breeze! 🚀

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Test Results

  1 files  ±0    1 suites  ±0   6m 17s ⏱️ +14s
595 tests ±0  554 ✅ ±0  41 💤 ±0  0 ❌ ±0 
610 runs  ±0  569 ✅ ±0  41 💤 ±0  0 ❌ ±0 

Results for commit e44f987. ± Comparison against base commit 09993bd.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files

📢 Thoughts on this report? Let us know!

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

app/components/track-leaderboard.ts (1)

Line range hint 71-71: Consider addressing the TODO comment.

The TODO comment indicates a need to move to a generic interface for handling both TrackLeaderboardEntry & TrackLeaderboardEntryModel. This could help eliminate the unknown type assertion used below.

Would you like me to help create this generic interface to resolve the TODO?

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 09993bd and e44f987.

📒 Files selected for processing (8)

• app/components/badges-page/badge-card.ts (2 hunks)
• app/components/concepts-page/concept-card.ts (2 hunks)
• app/components/header/account-dropdown.hbs (0 hunks)
• app/components/referrals-page/referral-links-container.hbs (0 hunks)
• app/components/track-leaderboard.ts (2 hunks)
• app/components/track-page/resume-track-button.ts (2 hunks)
• app/components/tracks-page/track-card.ts (2 hunks)
• app/controllers/catalog.ts (0 hunks)

💤 Files with no reviewable changes (3)

• app/components/referrals-page/referral-links-container.hbs
• app/components/header/account-dropdown.hbs
• app/controllers/catalog.ts

🔇 Additional comments (7)

app/components/concepts-page/concept-card.ts (1)

5-5: LGTM! Type safety improvements look good.

The addition of the type import and explicit parameter typing in the filter callback improves type safety without changing the runtime behavior.

Also applies to: 20-20

app/components/badges-page/badge-card.ts (1)

5-5: LGTM! Type safety improvements look good.

The addition of the type import and explicit parameter typing in the filter callback improves type safety without changing the runtime behavior.

Also applies to: 23-23

app/components/track-page/resume-track-button.ts (1)

8-8: LGTM! Type safety improvements look good.

The addition of the type import and type assertion for the filterBy results improves type safety without changing the runtime behavior.

Also applies to: 31-33

app/components/tracks-page/track-card.ts (1)

8-8: LGTM! Type safety improvements look good.

The addition of the type import and explicit parameter typing in the flatMap callback improves type safety without changing the runtime behavior.

Also applies to: 31-31

app/components/track-leaderboard.ts (3)

9-9: LGTM! Type import is correctly placed.

The import follows the established pattern of type imports and is properly organized with other similar imports.

---

56-58: LGTM! Type assertion improves type safety.

The type assertion as RepositoryModel[] properly types the filtered repositories array, helping TypeScript understand the exact type of the filtered results.

---

64-64: LGTM! Type annotation ensures type safety in reduce operation.

The explicit type annotation for the reduce accumulator and initial value improves type safety and prevents potential type-related issues.