fix(application-system): Fixing duplicate error, removing unused string

[Ballioli]

...

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

• Bug Fixes

  • Updated payment submit failed description message identifier.
  • Removed default institution label message from my pages applications.

• Refactor

  • Updated return type of resolveDataUri method in QualityPhotoResolver and QualitySignatureResolver classes to use lowercase string.

[coderabbitai]

Caution

Review failed

The head commit changed during the review from 8b79e51 to 7d31170.

Walkthrough

This pull request involves modifications to message definitions in multiple files within the application's libraries. In the libs/application/core/src/lib/messages.ts file, the id for the paymentSubmitFailedDescription message was updated. In the libs/portals/my-pages/applications/src/lib/messages.ts file, the defaultInstitutionLabel message was removed. Additionally, the return type of the resolveDataUri method in both the QualityPhotoResolver and QualitySignatureResolver classes was changed from Promise<String | null> to Promise<string | null>, reflecting a shift from the object wrapper to the primitive type in TypeScript.

Changes

File	Change Summary
libs/application/core/src/lib/messages.ts	Updated paymentSubmitFailedDescription message ID from application.system:core.payment.submitTitle to application.system:core.payment.paymentSubmitFailedDescription
libs/portals/my-pages/applications/src/lib/messages.ts	Removed defaultInstitutionLabel message with ID application.system:default-institution-label
libs/api/domains/driving-license/src/lib/graphql/qualityPhoto.resolver.ts, libs/api/domains/driving-license/src/lib/graphql/qualitySignature.resolver.ts	Updated resolveDataUri method return type from `Promise<String

Suggested labels

automerge, high priority

Suggested reviewers

• thorkellmani
• Toti91

---

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.

[datadog-island-is]

Datadog Report

All test runs a511974 🔗

✅ 9 Total Test Services: 0 Failed, 8 Passed
➡️ Test Sessions change in coverage: 14 no change

Test Services

Service Name	Failed	Known Flaky	New Flaky	Passed	Skipped	Total Time	Code Coverage Change	Test Service View
api	0	0	0	4	0	8.56s	1 no change	Link
application-core	0	0	0	97	0	39.82s	1 no change	Link
application-system-api	0	0	0	46	0	2m 55.95s	1 no change	Link
application-template-api-modules	0	0	0	85	0	0s	N/A	Link
application-ui-shell	0	0	0	72	0	0s	N/A	Link
judicial-system-backend	0	0	0	21219	0	13m 25.93s	1 no change	Link
services-auth-delegation-api	0	0	0	270	0	3m 40.8s	1 no change	Link
services-auth-personal-representative	0	0	0	0	0	291.35ms	1 no change	Link
web	0	0	0	84	0	57.31s	1 no change	Link

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

libs/api/domains/driving-license/src/lib/graphql/qualitySignature.resolver.ts (1)

25-25: LGTM! Consistent type usage.

The change maintains consistency with QualityPhotoResolver by using the primitive string type.

Consider extracting common resolver patterns into a shared base class or utility functions, as both QualityPhotoResolver and QualitySignatureResolver share similar structure and authorization logic.

Example base class pattern:

abstract class BaseQualityResolver<T> {
  constructor(protected readonly drivingLicenseService: DrivingLicenseService) {}

  @ResolveField('dataUri', () => String, { nullable: true })
  protected abstract resolveDataUri(
    @Parent() parent: T,
    @CurrentUser() user: User,
  ): Promise<string | null>;
}

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2302406 and 63c5a6d.

📒 Files selected for processing (2)

• libs/api/domains/driving-license/src/lib/graphql/qualityPhoto.resolver.ts (1 hunks)
• libs/api/domains/driving-license/src/lib/graphql/qualitySignature.resolver.ts (1 hunks)

🧰 Additional context used

📓 Path-based instructions (2)

libs/api/domains/driving-license/src/lib/graphql/qualitySignature.resolver.ts (1)

Pattern 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/api/domains/driving-license/src/lib/graphql/qualityPhoto.resolver.ts (1)

Pattern 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."

🔇 Additional comments (1)

libs/api/domains/driving-license/src/lib/graphql/qualityPhoto.resolver.ts (1)

25-25: LGTM! Good TypeScript practice.

The change from Promise<String> to Promise<string> aligns with TypeScript best practices by using primitive types instead of object wrappers.

Let's check for consistency across other resolvers:

✅ Verification successful

Verified: TypeScript primitive type usage is correct and consistent

The change from Promise<String> to Promise<string> in the resolver is an isolated improvement that follows TypeScript best practices. No other resolvers in the codebase use Promise<String>, and GraphQL schema definitions correctly use String type as required by the GraphQL specification.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for other resolvers that might need similar updates
ast-grep --pattern 'Promise<String' 

Length of output: 37

---

Script:

#!/bin/bash
# Search for Promise<String> type annotations in TypeScript files
rg "Promise<String>" --type ts -g "*resolver.ts" -g "*resolvers.ts"

# Search for String type usage in resolver files
rg ":\s*String\b" --type ts -g "*resolver.ts" -g "*resolvers.ts"

# Search for Promise<string> for comparison
rg "Promise<string>" --type ts -g "*resolver.ts" -g "*resolvers.ts"

Length of output: 206

---

Script:

#!/bin/bash
# Search for String type usage in all TypeScript files with context
rg ":\s*(Promise<)?String\b" --type ts -C 2

# Search for string type usage for comparison
rg ":\s*(Promise<)?string\b" --type ts -C 2

# Search in type definitions and schemas
rg "type.*String" --type ts --type graphql -C 2

Length of output: 66186

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 35.57%. Comparing base (27c57ef) to head (7d31170).

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17615      +/-   ##
==========================================
- Coverage   35.57%   35.57%   -0.01%     
==========================================
  Files        7031     7030       -1     
  Lines      150481   150486       +5     
  Branches    42970    42972       +2     
==========================================
  Hits        53536    53536              
- Misses      96945    96950       +5     

Flag	Coverage Δ
application-system-api	38.68% <ø> (ø)
judicial-system-backend	55.81% <ø> (ø)
services-auth-delegation-api	58.47% <ø> (ø)

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

Files with missing lines	Coverage Δ
libs/application/core/src/lib/messages.ts	100.00% <ø> (ø)

... and 11 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 27c57ef...7d31170. Read the comment docs.