Development: Remove unused participation and repository caching from routing modules

[SimonEntholzer]

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.

Client

• Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data (e.g. using paging).
• I strictly followed the principle of data economy for all client-server REST calls.
• I strictly followed the client coding and design guidelines.

Motivation and Context

In several routing module files there is unused code for caching the participation and repository.

 flushRepositoryCacheAfter: 900000, // 15 min
            participationCache: {},
            repositoryCache: {},

Description

This PR removes this unused code, as it serves no purpose.

Steps for Testing

1. Login and check that the routing to repositories with the code button still works

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

Manual Tests

• Test 1
• Test 2

Summary by CodeRabbit

• New Features
  • Streamlined routing configuration for exam management and programming exercises by removing unnecessary cache management properties.
• Bug Fixes
  • Improved routing logic by eliminating redundant data properties, potentially enhancing performance and data handling.

[coderabbitai]

Walkthrough

The pull request introduces modifications to the routing configuration across multiple modules in an Angular application, specifically related to exam management and programming exercises. The key change involves the removal of cache management properties—flushRepositoryCacheAfter, participationCache, and repositoryCache—from various route definitions. This affects routes associated with student exam summaries, commit history, and repository views, streamlining the routing logic without altering the overall structure or components.

Changes

File Path	Change Summary
src/main/webapp/app/exam/manage/exam-management.route.ts	Removed flushRepositoryCacheAfter, participationCache, and repositoryCache from multiple routes related to exam management.
src/main/webapp/app/exercises/programming/manage/code-editor/code-editor-management-routing.module.ts	Removed flushRepositoryCacheAfter, participationCache, and repositoryCache from all route definitions in the code editor management module.
src/main/webapp/app/exercises/programming/manage/programming-exercise-management-routing.module.ts	Removed cache management properties from routes handling repository views, commit histories, and access logs.
src/main/webapp/app/exercises/programming/participate/programming-participation-routing.module.ts	Removed flushRepositoryCacheAfter, participationCache, and repositoryCache from the route using CodeEditorStudentContainerComponent.
src/main/webapp/app/exercises/programming/participate/programming-repository-routing.module.ts	Removed cache management properties from routes related to repository viewing and commit history.

Possibly related PRs

• Exam mode: Fix navigation when clicking open repository #8898: Modifies routing configurations related to repository views and commit history, similar to the main PR's changes in routing for exam management.
• Development: Fix the broken git programming submission e2e tests #9546: Involves changes to the ProgrammingExerciseParticipationService, which may indirectly relate to the routing changes in the main PR by affecting participation data handling.
• Development: Improve performance of programming exercise details view #9785: Enhances the performance of the programming exercise details view, potentially relating to the overall routing and data handling improvements in the main PR.
• Programming exercises: Fix an issue with the access log in exam exercises #9872: Adds new routes for VCS access logs in exam mode, directly related to the routing changes made in the main PR for exam management.

Suggested labels

ready for review, chore, code quality, refactoring, bugfix

Suggested reviewers

• florian-glombik
• muradium
• krusche
• BBesrour

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 4eaba4e and be4128d.

📒 Files selected for processing (5)

• src/main/webapp/app/exam/manage/exam-management.route.ts (0 hunks)
• src/main/webapp/app/exercises/programming/manage/code-editor/code-editor-management-routing.module.ts (0 hunks)
• src/main/webapp/app/exercises/programming/manage/programming-exercise-management-routing.module.ts (0 hunks)
• src/main/webapp/app/exercises/programming/participate/programming-participation-routing.module.ts (0 hunks)
• src/main/webapp/app/exercises/programming/participate/programming-repository-routing.module.ts (0 hunks)

💤 Files with no reviewable changes (5)

• src/main/webapp/app/exam/manage/exam-management.route.ts
• src/main/webapp/app/exercises/programming/manage/code-editor/code-editor-management-routing.module.ts
• src/main/webapp/app/exercises/programming/manage/programming-exercise-management-routing.module.ts
• src/main/webapp/app/exercises/programming/participate/programming-participation-routing.module.ts
• src/main/webapp/app/exercises/programming/participate/programming-repository-routing.module.ts

---

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.

[PaRangger]

Tested on TS1, routing still works for me. Code LGTM 👍

[sachmii]

Tested on TS1, routing works fine.

[HawKhiem]

Tested on TS5. Routing still works as mentioned

[cremertim]

Lgtm

[BBesrour]

code

[coolchock]

code