Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(j-s): Update advocate confirmed strings #16573

Merged
merged 2 commits into from
Oct 28, 2024
Merged

Conversation

unakb
Copy link
Member

@unakb unakb commented Oct 25, 2024

Textar í modal þegar verið er að staðfesta/breyta verjanda

What

Updated some texts and force update them in contentful

Why

To keep our code in sync with Contentful values

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

    • Updated localization strings for the court indictments section, enhancing clarity and consistency.
    • Introduced versioning in identifiers for better management of localization entries.
  • Bug Fixes

    • Improved default messages for various modal texts to ensure better understanding for users.

@unakb unakb requested a review from a team as a code owner October 25, 2024 14:36
Copy link
Contributor

coderabbitai bot commented Oct 25, 2024

Walkthrough

The pull request introduces updates to the Advocates.strings.ts file, focusing on localization strings within the judicial system's court indictments section. Modifications include the addition of versioning to existing identifiers and the rephrasing of default messages for clarity. Key identifiers such as confirmDefenderChoice and changeDefenderChoice have been updated to include a version suffix, reflecting a systematic approach to enhancing clarity and consistency in the localization strings.

Changes

File Path Change Summary
apps/judicial-system/web/src/routes/Court/Indictments/Advocates/Advocates.strings.ts Updated localization identifiers to include versioning (e.g., confirm_defender_choice to confirm_defender_choice_v1). Default messages have been rephrased for clarity.

Possibly related PRs

Suggested labels

automerge

Suggested reviewers

  • oddsson

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (3)
apps/judicial-system/web/src/routes/Court/Indictments/Advocates/Advocates.strings.ts (3)

28-32: LGTM! Consider documenting the versioning strategy.

The addition of version suffix '_v1' to the string identifier is a good practice for managing content updates. However, it would be beneficial to document this versioning strategy in the project documentation for future maintainers.


166-167: LGTM! Consider enhancing type safety.

While the versioning update is good, consider creating a TypeScript type or const enum for the version suffixes to ensure consistency across the codebase.

Example implementation:

export const STRING_VERSIONS = {
  V1: '_v1'
} as const;

type StringVersion = typeof STRING_VERSIONS[keyof typeof STRING_VERSIONS];

Line range hint 1-190: Consider implementing a versioning strategy document.

The systematic addition of version suffixes to string identifiers indicates a need for:

  1. A documented versioning strategy
  2. Type-safe version management
  3. A migration guide for future version updates
  4. Integration with the content management workflow

This will help maintain consistency and make future updates more manageable.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 40cffdf and e9d9476.

📒 Files selected for processing (1)
  • apps/judicial-system/web/src/routes/Court/Indictments/Advocates/Advocates.strings.ts (4 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
apps/judicial-system/web/src/routes/Court/Indictments/Advocates/Advocates.strings.ts (1)

Pattern apps/**/*: "Confirm that the code adheres to the following:

  • NextJS best practices, including file structure, API routes, and static generation methods.
  • Efficient state management and server-side rendering techniques.
  • Optimal use of TypeScript for component and utility type safety."
🔇 Additional comments (3)
apps/judicial-system/web/src/routes/Court/Indictments/Advocates/Advocates.strings.ts (3)

37-38: LGTM! Consistent with versioning pattern.

The changes maintain consistency with the new versioning approach while preserving the message semantics.


126-128: Verify translation requirements for system-specific terms.

The message now includes the system name "Réttarvörslugátt". Ensure that:

  1. This term is consistently used across the application
  2. Translation requirements for this system-specific term are communicated to translators

139-141: LGTM! Message maintains clarity.

The versioned identifier and rephrased message maintain the intended meaning while aligning with content management updates.

Copy link

codecov bot commented Oct 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.80%. Comparing base (ab7895e) to head (e9d9476).
Report is 17 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main   #16573      +/-   ##
==========================================
- Coverage   36.80%   36.80%   -0.01%     
==========================================
  Files        6854     6854              
  Lines      142236   142227       -9     
  Branches    40561    40558       -3     
==========================================
- Hits        52346    52342       -4     
+ Misses      89890    89885       -5     
Flag Coverage Δ
judicial-system-api 19.42% <ø> (+0.08%) ⬆️
judicial-system-backend 55.31% <ø> (-0.01%) ⬇️
judicial-system-formatters 79.82% <ø> (+0.04%) ⬆️
judicial-system-message 67.37% <ø> (ø)
judicial-system-message-handler 48.53% <ø> (ø)
judicial-system-scheduler 70.52% <ø> (+0.04%) ⬆️
judicial-system-types 44.09% <ø> (-0.14%) ⬇️
judicial-system-web 27.79% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
...s/Court/Indictments/Advocates/Advocates.strings.ts 0.00% <ø> (ø)

... and 8 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ab7895e...e9d9476. Read the comment docs.

@datadog-island-is
Copy link

datadog-island-is bot commented Oct 25, 2024

Datadog Report

Branch report: j-s/advocate-strings
Commit report: c6b3a6e
Test service: judicial-system-web

✅ 0 Failed, 288 Passed, 0 Skipped, 0s Total Time

@oddsson oddsson added the automerge Merge this PR as soon as all checks pass label Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge this PR as soon as all checks pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants