Development: Fix the path of exercise- and lecture-type domain objects in the client

[ole-ve]

Checklist

General

• I tested all changes and their related features with all corresponding user types on a test server.
• This is a small issue that I tested locally and was confirmed by another developer on a test server.
• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

After changing the server folder structure, the path to the exercise- and lecture-type domain objects are wrong in the client.

Description

Correct the path in the client.

Testserver States

Note

These badges show the state of the test servers.
Green = Currently available, Red = Currently locked
Click on the badges to get to the test servers.

Review Progress

Code Review

• Code Review 1
• Code Review 2

Summary by CodeRabbit

• New Features

  • Updated identifiers for exercise types and lecture unit types to improve clarity and maintainability.

• Bug Fixes

  • Adjusted mapping methods to align with the new package structure, ensuring accurate type recognition for exercises and lecture units.

[coderabbitai]

Walkthrough

The changes in this pull request involve updates to the CourseDashboardService class, specifically altering string literals for exercise types and lecture unit types. The updates reflect a new package structure, changing references from de.tum.cit.aet.artemis.domain to de.tum.cit.aet.artemis.lecture.domain. The modifications affect the mapToExerciseType and mapToLectureUnitType methods, ensuring that the logic for mapping types remains unchanged while improving clarity in the codebase.

Changes

Files	Change Summary
src/main/webapp/app/overview/course-dashboard/course-dashboard.service.ts	Updated string literals in mapToExerciseType and mapToLectureUnitType methods to reflect new package structure.

Possibly related PRs

• Exam mode: Show exercise group title in breadcrumbs #9254: The changes in the CourseManagementService and ProgrammingExerciseParticipationService involve updates to how exercise titles are set, which may relate to the overall effort of standardizing naming conventions and improving maintainability in the codebase, similar to the changes made in the CourseDashboardService.

Suggested labels

client, small, bugfix, ready to merge

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

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 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 or @coderabbitai title anywhere in the PR title to generate the title automatically.

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.

[pzdr7]

Code

[coolchock]

code