i accidently removed some code when i merged

[gurkvatten]

Summary by CodeRabbit

• Refactor

  • Updated internal system relationship configurations to improve data structure alignment

• Bug Fixes

  • Fixed administrative navigation link to properly direct to the Reports dashboard

[coderabbitai]

📝 Walkthrough

Walkthrough

Two configuration updates: the Cases entity's join table mapping for accounts was updated to use report_id instead of case_id, and the admin link in the userpage template was changed from a static /private path to a Thymeleaf-resolved /reports route.

Changes

Cohort / File(s)	Summary
JPA Entity Mapping src/main/java/org/example/crimearchive/cases/Cases.java	Updated @JoinColumn name from case_id to report_id in the many-to-many relationship with accounts, affecting the join table column reference.
HTML Template src/main/resources/templates/userpage.html	Changed admin-link href from static relative path /private to Thymeleaf-resolved expression @{/reports} for dynamic route resolution.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Possibly related PRs

• Feature/profile #17 — Modifies the same Cases.accounts JPA @JoinTable and @JoinColumn configuration, directly related to the join column name change.

Poem

🐰 A hop through the mappings, a link made anew,
From case_id to report_id, the join table grew,
The admin path dances from /private to /reports so fine,
With Thymeleaf's grace, all the routes now align! 🌿

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title is vague and generic, using informal language ('i accidently') without describing the specific changes made to the codebase.	Revise the title to be more specific and professional, such as 'Fix join column mapping and update admin link routing' to clearly describe the actual changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fixes-after-merge

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/main/java/org/example/crimearchive/cases/Cases.java`:
- Around line 20-26: In the Cases.accounts mapping update the join column name
used in joinColumns from "report_id" to "case_id" so the account_cases join
table references the Cases entity correctly: locate the `@ManyToMany/`@JoinTable
block on the Cases.accounts field and change joinColumns = `@JoinColumn`(name =
"report_id") to joinColumns = `@JoinColumn`(name = "case_id") to align the
generated schema with the Cases primary key mapping.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 4805a91d-0bcd-4160-9eb2-3f4b7edb5b7c

📥 Commits

Reviewing files that changed from the base of the PR and between e17c105 and 8561039.

📒 Files selected for processing (2)

• src/main/java/org/example/crimearchive/cases/Cases.java
• src/main/resources/templates/userpage.html