Exam mode: Update problem statement content only if there is a new change

[kaancayli]

Checklist

General

• 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.
• I strictly followed the client coding and design guidelines.
• I documented the TypeScript code using JSDoc style.
• I added multiple screenshots/screencasts of my UI changes.

Motivation and Context

After submitting the exam, "Click Show the difference" button can still be seen on the exam overview page and clicking the button does not show any difference. This PR makes sure that after submission, the button is not visible.

Description

Changed the BehaviorSubject to regular Subject in exam-exercise-update.service.ts

Exam Mode Testing

Prerequisites:

• 1 Instructor
• 1 Student
• 1 Exam with a Programming Exercise

Note

Prevent refreshing your browser while following the steps.

1. Log in to Artemis
2. Participate in an exam as a student
3. In another browser / or in a new window using incognito mode, log in to Artemis as an Instructor / Admin.
4. Go to exam management as instructor and edit the problem statement of the programming exercise.
5. As student verify that you can see the "Click Show the difference" button, and clicking the button shows the difference.
6. Make a submission to the programming exercise as a student.
7. After your submission is built and tested, hand in the exam
8. Verify on the exam overview page that "Click Show the difference" button is not visible.

Testserver States

Note

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

Review Progress

Code Review

• Code Review 1
• Code Review 2

Exam Mode Test

• Test 1
• Test 2

Screenshots

• Before submission:
  

• After submission:
  

[coderabbitai]

Walkthrough

The recent updates aim to enhance the user experience in exam exercises by refining the problem statement update process and improving update visibility. These changes involve adjusting service behaviors, updating HTML templates for better UI control, and introducing properties for managing component visibility. The goal is to facilitate clearer communication of updates and modifications within exam exercises.

Changes

Files	Change Summary
.../exam/manage/exam-exercise-update.service.ts	Replaced BehaviorSubject with Subject for examExerciseIdAndProblemStatementSource
.../participate/exercises/exam-exercise-update-highlighter.component.html .../participate/exercises/exam-exercise-update-highlighter.component.ts	Updated HTML template and component logic to control button visibility based on _isHidden property

Possibly related issues

• Exam mode: Problem statement diff view does only show diff to last change #7567: The modifications could contribute to a clearer diff view by changing how updates are managed and displayed.
• Highlight differences in Exam Timeline #7197: Enhancements in update visibility and management may indirectly support the objectives of highlighting differences in exam timelines.
• Problem statement in the programming exercise detail page is not showing the template repo status correctly #7880: Changes in the update mechanism could ensure consistent display of the latest submission status, potentially addressing the objectives outlined in this issue.

---

Recent Review Details

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 99617ce and 441a45e.

Files selected for processing (1)

• src/main/webapp/app/exam/participate/exercises/exam-exercise-update-highlighter/exam-exercise-update-highlighter.component.html (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• src/main/webapp/app/exam/participate/exercises/exam-exercise-update-highlighter/exam-exercise-update-highlighter.component.html

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[Strohgelaender]

code

[JohannesWt]

Code looks good

[julian-christl]

Don't see any such button on TS2, code lgtm

[coolchock]

tested during testing session, works as described 👍

[undernagruzez]

tested during the testing session today, works as expected

[egekurt123]

Manually Tested during testing session on ts4, works as expected

[pzdr7]

Tested in testing session; works as expected

[BaumiCoder]

Successfully tested in the Testing Session 👍