Programming exercises: Fix error details modal in feedback analysis table

[az108]

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

This PR fixes the following issue (#10414) found in a recent exam grading. In rare cases, when a test case had a name that was too long, the modal would overflow.

Description

The text now breaks in case of excessively long test case names.

Steps for Testing

Prerequisites:

• 1 Instructor
• 1 Student
• 1 Programming Exercise

1. Log in to Artemis
2. Navigate to a Course with Instructor rights
3. Create a Programming Exercise or use an existing one without a due date
4. Modify one TestCase to fail guaranteed and give it a very long testCaseName
5. Solve the Programming Exercise as Student
6. Navigate as Instructor to the Grading of an Exercise
7. Navigate to the Feedback Analysis section
8. Verify that after you open the detailed feedback view modal (first icon from the 3 icons on the right for one entry in the table) you see all items in the modal

Testserver States

You can manage test servers using Helios. Check environment statuses in the environment list. To deploy to a test server, go to the CI/CD page, find your PR or branch, and trigger the deployment.

Review Progress

Performance Review

Code Review

• Code Review 1

Manual Tests

• Test 1

Screenshots

Before:

After:

[coderabbitai]

Walkthrough

This change updates the HTML template of a feedback modal component to enhance text display. Specifically, the detailTemplate section's <div> element now includes the text-break class alongside existing classes. This modification affects how text wraps within the component without altering the underlying logic or data bindings.

Changes

File Path	Change Summary
src/.../feedback-modal.component.html	Updated the <div> element in the detailTemplate ng-template to include the text-break class for better text wrapping.

Suggested labels

bugfix, client, ready to merge, small

Suggested reviewers

• ItsaaaMeMario
• EneaGore
• BBesrour
• krusche
• coolchock

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 06f2da4 and e055dc2.

📒 Files selected for processing (1)

• src/main/webapp/app/exercises/programming/manage/grading/feedback-analysis/modal/feedback-modal.component.html (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

`src/main/webapp/**/*.html`: @if and @for are new and valid ...

src/main/webapp/**/*.html: @if and @for are new and valid Angular syntax replacing *ngIf and *ngFor. They should always be used over the old style.

• src/main/webapp/app/exercises/programming/manage/grading/feedback-analysis/modal/feedback-modal.component.html

⏰ Context from checks skipped due to timeout of 90000ms (9)

• GitHub Check: Call Build Workflow / Build and Push Docker Image
• GitHub Check: Call Build Workflow / Build .war artifact
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: client-style
• GitHub Check: client-tests
• GitHub Check: server-style
• GitHub Check: server-tests
• GitHub Check: Analyse
• GitHub Check: Mend Security Check

🔇 Additional comments (1)

src/main/webapp/app/exercises/programming/manage/grading/feedback-analysis/modal/feedback-modal.component.html (1)

31-31: Enhance text wrapping with text-break class.

The addition of the text-break class to the <div> element ensures that long test case names wrap properly within the error details modal, effectively addressing the overflow issue. This change meets the PR objectives and follows the styling conventions without impacting the existing layout or functionality.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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 generate docstrings to generate docstrings for this 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.

[magaupp]

Code looks good