fix(CaseOverview): UBO risk indicator title

[shanegrouber]

• Ensure 'ubos' case returns the correct tab name

The notion rules had 'Domain' as 'UBOs'

const domain = 'UBOs'
console.log(camelCase(domain))
> 'ubOs'

This does not match the mapping in TabToLabel because of

title: TabToLabel[tab as keyof typeof TabToLabel] ?? titleCase(domain ?? '')

so it would default back to use:

console.log(titleCase(camelCase(domain)))
> 'UB Os'

Summary by CodeRabbit

• New Features

  • Improved the consistency of tab names in the Case Overview, ensuring certain domain labels display as intended.

• Chores

  • Streamlined internal commit processing by excluding unnecessary lock file changes from version control diffs.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4718dc9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

This update refines tab name generation in the CaseOverview component and adjusts the git diff command in the auto-commit script. A new helper function getTab now checks whether the domain is 'ubos' to return it directly, or converts it using camelCase otherwise. Additionally, the auto-commit script excludes changes in pnpm-lock.yaml from the diff output.

Changes

File(s)	Change Summary
apps/backoffice-v2/.../CaseOverview.tsx	Added the getTab(domain: string) function, which returns "ubos" when the domain is 'ubos' or applies camelCase otherwise, for tab naming.
scripts/auto-commit.js	Updated the git diff command to git diff --cached -- . ":(exclude)pnpm-lock.yaml", excluding changes in pnpm-lock.yaml from processing.

Sequence Diagram(s)

sequenceDiagram
  participant Component as CaseOverview Component
  participant getTab as getTab()
  participant camelCase as camelCase()

  Component->>getTab: Call with domain value
  alt Domain is "ubos"
    getTab-->>Component: Return "ubos"
  else
    getTab->>camelCase: Convert domain to camelCase
    camelCase-->>getTab: Return converted string
    getTab-->>Component: Return camelCase string
  end

Loading

sequenceDiagram
  participant Script as auto-commit Script
  participant Git as Git Diff Command

  Script->>Git: Execute `git diff --cached -- . ":(exclude)pnpm-lock.yaml"`
  Git-->>Script: Return diff excluding pnpm-lock.yaml changes

Loading

Suggested reviewers

• Omri-Levy
• MatanYadaev

Poem

I'm a rabbit with a coder's delight,
Hopping through changes both day and night.
With getTab leaping logic so true,
And auto-commit filtering old from new.
My whiskers twitch in lines of code—
A playful dance along the debugging road!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 130b240 and 4718dc9.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• apps/backoffice-v2/src/pages/Entity/components/Case/components/CaseOverview/CaseOverview.tsx (1 hunks)
• scripts/auto-commit.js (1 hunks)

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

• GitHub Check: Analyze (javascript)

🔇 Additional comments (2)

apps/backoffice-v2/src/pages/Entity/components/Case/components/CaseOverview/CaseOverview.tsx (1)

31-38: LGTM! The changes effectively fix the tab name issue for 'ubos' cases.

The new getTab function correctly handles the special case for 'ubos' by returning it directly, while maintaining the existing camelCase transformation for other domains. This aligns with the PR objective and resolves the tab name mismatch.

scripts/auto-commit.js (1)

78-78: Consider separating unrelated changes into a different PR.

While excluding pnpm-lock.yaml from the diff output is a good practice, this change is unrelated to fixing the tab name issue for 'ubos' cases. Consider moving this change to a separate PR to maintain clear change history and facilitate easier reviews.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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 anywhere in the PR title to generate the title automatically.

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