Development: Use a record for TutorialGroupFreePeriodDTO

[Jan-Thurner]

Checklist

General

• This is a small issue that I tested locally and was confirmed by another developer on a test server.(https://docs.artemis.cit.tum.de/dev/guidelines/language-guidelines/).
• I chose a title conforming to the naming conventions for pull requests.

Server

• I strictly followed the server coding and design guidelines.
• I documented the Java code using JavaDoc style.

Motivation and Context

The changes adopt theTutorialGroupFreePeriodDTO to follow the server coding guidelines. This PR improves quality and consistency throughout the code base.

Description

The TutorialGroupFreePeriodDTO is now a record and not a Java class anymore. The affected parts of the code were modified to conform to that change.

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

Test Coverage

Class/File	Line Coverage	Confirmation (assert/expect)
TutorialGroupFreePeriodResource.java	92%	✅

Summary by CodeRabbit

• Refactor
  • Transitioned TutorialGroupFreePeriodDTO to a record class for more efficient data handling.
• Changes
  • Updated method calls and imports in TutorialGroupFreePeriodResource to align with the new record class structure.
  • Modified integration tests to reflect changes in method naming conventions and class references for TutorialGroupFreePeriod.

[coderabbitai]

Walkthrough

The update primarily focuses on enhancing the TutorialGroupFreePeriod functionality within a Java project. It introduces a new TutorialGroupFreePeriodDTO directly within the TutorialGroupFreePeriodResource file, adjusting for changes by adding necessary imports and annotations. Correspondingly, the integration test file reflects these modifications by updating imports and adjusting the use of TutorialGroupFreePeriodDTO to align with its new declaration location.

Changes

Files	Summary of Changes
.../web/rest/tutorialgroups/TutorialGroupFreePeriodResource.java	- Refactored TutorialGroupFreePeriodDTO class to a record class with constructor parameters - Updated method calls to use methods instead of direct field access - Added @JsonInclude annotation
.../tutorialgroups/TutorialGroupFreePeriodIntegrationTest.java	- Replaced import of TutorialGroupFreePeriodDTO with TutorialGroupFreePeriodResource - Updated method calls to use lowercase method names for startDate(), endDate(), and reason() - Updated references to TutorialGroupFreePeriodDTO within the class

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-tests 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 tests 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 tests.
  • @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.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[Strohgelaender]

I think the DTO should still be its own file, just as a record instead of a class file.

[Kroko-fant]

Code looks good to me

[rstief]

Code LGTM