chore(application-system): Added work accident notification scope to list of requested scopes

[jonarnarbriem]

Adding work accident notification scope to list of requested scopes in application system.

...

Attach a link to issue if relevant

What

Specify what you're trying to achieve

Why

Specify why you need to achieve this

Screenshots / Gifs

Attach Screenshots / Gifs to help reviewers understand the scope of the pull request

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• Formatting passes locally with my changes
• I have rebased against main before asking for a review

Summary by CodeRabbit

• New Features
  • Enhanced the system's accident management capabilities, improving incident tracking and response.

[coderabbitai]

Walkthrough

This pull request updates the applicationSystemScopes array in the libs/auth/scopes/src/lib/clients/application-system-scopes.ts file by adding a new entry: ApiScope.vinnueftirlitidAccident. The change expands the set of API scopes to include accident management capabilities. No other modifications to the array or its structure are present.

Changes

File Path	Change Summary
libs/auth/.../application-system-scopes.ts	Added new entry ApiScope.vinnueftirlitidAccident to the API scopes array

Possibly related PRs

• fix(auth-api-lib): add TR scopes for application system #15179: Involves modifications to application system scopes, directly relating to the addition of a new scope.
• fix(application-system): Error messages, input validation, code cleanup #17571: Updates the requiredScopes property to include ApiScope.vinnueftirlitidAccident, directly connecting to this change.

Suggested labels

automerge

Suggested reviewers

• thorkellmani
• HjorturJ

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

📜 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 5188d0e and 1609f4e.

📒 Files selected for processing (1)

• libs/auth/scopes/src/lib/clients/application-system-scopes.ts (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

`libs/**/*`: "Confirm that the code adheres to the following...

libs/**/*: "Confirm that the code adheres to the following:

• Reusability of components and hooks across different NextJS apps.
• TypeScript usage for defining props and exporting types.
• Effective tree-shaking and bundling practices."

• libs/auth/scopes/src/lib/clients/application-system-scopes.ts

🔇 Additional comments (1)

libs/auth/scopes/src/lib/clients/application-system-scopes.ts (1)

22-22: LGTM! The new scope is logically placed.

The new scope vinnueftirlitidAccident is appropriately placed next to the related scope vinnueftirlitid, maintaining good code organization.

Let's verify that the new scope is properly defined in the ApiScope enum:

✅ Verification successful

🏁 Script executed:

#!/bin/bash
# Description: Check if the new scope is defined in the ApiScope enum
# and follows the naming convention of other scopes

ast-grep --pattern 'enum ApiScope {
  $$$
  vinnueftirlitidAccident = $_,
  $$$
}'

Length of output: 3402

---

Scope Definition Verified

The new scope vinnueftirlitidAccident is correctly defined in the ApiScope enum (located in libs/auth/scopes/src/lib/api.scope.ts) and follows the naming conventions consistent with related scopes.

✨ 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.

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.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 1609f4e.

Command	Status	Duration	Result
nx run-many --target=codegen/frontend-client --...	✅ Succeeded	11s	View ↗
nx run-many --target=codegen/backend-schema --a...	✅ Succeeded	1m 49s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-02-06 08:47:41 UTC