Skip to content

Conversation

@vishwab1
Copy link
Member

@vishwab1 vishwab1 commented Jun 17, 2025

πŸ“‹ Description

JIRA ID: AMM-1246

Please provide a summary of the change and the motivation behind it. Include relevant context and details.


βœ… Type of Change

  • 🐞 Bug fix (non-breaking change which resolves an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • πŸ”₯ Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • πŸ›  Refactor (change that is neither a fix nor a new feature)
  • βš™οΈ Config change (configuration file or build script updates)
  • πŸ“š Documentation (updates to docs or readme)
  • πŸ§ͺ Tests (adding new or updating existing tests)
  • 🎨 UI/UX (changes that affect the user interface)
  • πŸš€ Performance (improves performance)
  • 🧹 Chore (miscellaneous changes that don't modify src or test files)

ℹ️ Additional Information

Please describe how the changes were tested, and include any relevant screenshots, logs, or other information that provides additional context.

Summary by CodeRabbit

  • New Features

    • Introduced configurable CORS (Cross-Origin Resource Sharing) support, allowing dynamic control over permitted origins via external configuration.
  • Refactor

    • Centralized CORS configuration, removing individual CORS annotations from all controllers.
    • Enhanced filter logic to handle CORS headers and preflight requests based on allowed origins.
  • Chores

    • Updated configuration files to include new CORS settings for easier customization.

@coderabbitai
Copy link

coderabbitai bot commented Jun 17, 2025

Warning

Rate limit exceeded

@vishwab1 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 17 minutes and 7 seconds before requesting another review.

βŒ› How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 685609c and ae7ec1f.

πŸ“’ Files selected for processing (2)
  • src/main/environment/ecd_ci.properties (1 hunks)
  • src/main/java/com/iemr/ecd/utils/mapper/JwtUserIdValidationFilter.java (3 hunks)

Walkthrough

This change centralizes and enhances CORS (Cross-Origin Resource Sharing) configuration. It removes all @CrossOrigin annotations from controller classes, introduces dynamic allowed origins via configuration properties, and updates both the global web configuration and the JWT validation filter to set CORS headers based on these properties.

Changes

File(s) Change Summary
src/main/environment/ecd_ci.properties, src/main/environment/ecd_example.properties Added new cors.allowed-origins property for dynamic CORS origin configuration.
src/main/java/com/iemr/ecd/config/WebConfiguration.java Enhanced CORS setup: reads allowed origins from config, restricts methods, exposes headers, logs origins, and updates method.
src/main/java/com/iemr/ecd/utils/mapper/FilterConfig.java Injects allowedOrigins property, passes it to JWT filter, and sets filter order to highest precedence.
src/main/java/com/iemr/ecd/utils/mapper/JwtUserIdValidationFilter.java Adds allowed origins parameter, sets CORS headers dynamically, supports wildcards, and handles preflight OPTIONS requests.
src/main/java/com/iemr/ecd/controller/.../*.java (all controller files listed) Removes all @CrossOrigin annotations and related imports from controller classes and methods. Minor formatting adjustments only.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Filter as JwtUserIdValidationFilter
    participant WebConfig as WebConfiguration
    participant Controller

    Client->>Filter: HTTP Request (with Origin header)
    Filter->>Filter: Check if Origin is allowed
    alt Origin allowed
        Filter->>Client: Set CORS headers in response
    else Origin not allowed
        Filter->>Client: No CORS headers, log warning
    end
    alt OPTIONS request
        Filter->>Client: Respond 200 OK (preflight)
    else
        Filter->>Controller: Forward request for processing
        Controller-->>Filter: Response
        Filter->>Client: Forward response (with CORS headers if allowed)
    end
Loading

Possibly related PRs

  • PSMRI/ECD-API#60: Implements a similar global CORS configuration by removing @CrossOrigin annotations and introducing centralized, property-based CORS setup.

Suggested reviewers

  • ravishanigarapu
  • sandipkarmakar3

Poem

In the warren of code, a new breeze blows,
CORS is now smarter, as every bunny knows!
From scattered annotations, we now abstain,
With origins set in configβ€”much less pain.
Hop, hop, hooray! The headers align,
Cross-origin requests now handled just fine.
πŸ‡βœ¨

✨ Finishing Touches
  • πŸ“ Generate Docstrings

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
πŸͺ§ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.

Copy link

@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: 2

πŸ”­ Outside diff range comments (1)
src/main/java/com/iemr/ecd/repo/call_conf_allocation/OutboundCallsRepo.java (1)

124-131: Parameter order in count query differs from select query

getMotherUnAllocatedCountHR no longer takes fDate/tDate while the count-LR versions do. Paging components that rely on counts vs. list queries may display mismatched totals. Align the signatures or document the difference explicitly.

♻️ Duplicate comments (4)
src/main/java/com/iemr/ecd/controller/quality/ChartsController.java (1)

42-48: Same CORS centralisation caveat as previous controller

The observations & script in the previous comment apply to this controller as well.
No further issues spotted.

src/main/java/com/iemr/ecd/controller/quality/AgentQualityAuditorMappingController.java (1)

45-51: Same CORS centralisation caveat as previous controller

See the first review comment for checks to perform.

src/main/java/com/iemr/ecd/controller/associate/AutoPreviewDialingController.java (1)

45-51: Same CORS centralisation caveat as previous controller

See the first review comment for checks to perform.

src/main/java/com/iemr/ecd/controller/callallocation/CallAllocationController.java (1)

49-55: Same CORS centralisation caveat as previous controller

See the first review comment for checks to perform.

🧹 Nitpick comments (10)
src/main/java/com/iemr/ecd/controller/callallocation/CallAllocationController.java (1)

156-160: Readability nit – long parameter list

The wrapped call is easier to read now, but seven positional String parameters are still error-prone. Consider introducing a small DTO for this request to improve maintainability.

src/main/java/com/iemr/ecd/controller/quality/QualityAuditController.java (1)

91-93: Prefer using ResponseEntity.ok(…) for brevity

The explicit constructor call is perfectly valid, but the more idiomatic Spring style is the static helper:

-		return new ResponseEntity<>(
-				qualityAuditImpl.getQualityAuditorWorklistDatewise(qualityAuditorWorklistDatewiseRequestDTO),
-				HttpStatus.OK);
+		return ResponseEntity.ok(
+				qualityAuditImpl.getQualityAuditorWorklistDatewise(qualityAuditorWorklistDatewiseRequestDTO));

Same payload, cleaner code.

src/main/java/com/iemr/ecd/controller/outboundworklist/OutBoundWorklistController.java (1)

69-71: Minor stylistic tweak – replace verbose constructor with helper

-		return new ResponseEntity<>(resp, HttpStatus.OK);
+		return ResponseEntity.ok(resp);

No behavioural change, just terser.

src/main/java/com/iemr/ecd/controller/masters/MastersController.java (1)

238-244: authorization header collected but never used

The method demands an Authorization header yet immediately discards it, which:

  1. Creates dead-code noise.
  2. Forces callers to send a header that serves no purpose.
  3. Risks forgetting to forward the token to the service layer if that becomes necessary later.

Either drop the parameter or forward it:

-public ResponseEntity<List<AgentsViewMaster>> getAgentsByRoleIdAndLanguage(
-		@RequestHeader(value = "Authorization") String authorization, @PathVariable Integer roleId,
-		@PathVariable String preferredLanguage) {
-	return new ResponseEntity<>(masterServiceImpl.getAgentByRoleIdAndLanguage(roleId, preferredLanguage),
-			HttpStatus.OK);
+public ResponseEntity<List<AgentsViewMaster>> getAgentsByRoleIdAndLanguage(
+		@PathVariable Integer roleId,
+		@PathVariable String preferredLanguage) {
+	return ResponseEntity.ok(
+			masterServiceImpl.getAgentByRoleIdAndLanguage(roleId, preferredLanguage));
}

If the service really needs the token, pass it explicitly; otherwise the parameter and its annotation can be safely deleted.

src/main/java/com/iemr/ecd/config/WebConfiguration.java (2)

37-55: Guard against empty / wildcard cors.allowed-origins

If cors.allowed-origins is empty or contains only a wildcard, originPatterns becomes [""], effectively allowing no origins. This is a silent foot-gun on fresh deployments.

Add a fallback:

String[] originPatterns = Arrays.stream(allowedOrigins.split(","))
        .map(String::trim)
        .filter(s -> !s.isEmpty())
        .toArray(String[]::new);

if (originPatterns.length == 0) {
    originPatterns = new String[] {"*"};   // or log and fail fast
}

Also consider externalising allowed methods to config so ops can adjust without a code change.


46-54: Minor: use allowedOrigins over allowedOriginPatterns when wildcards are not required

allowedOriginPatterns disables CORS pre-flight optimisation for exact matches and is only needed for wildcard domains. If you never expect wildcards, prefer .allowedOrigins(originPatterns) – it is stricter and marginally faster.

src/main/java/com/iemr/ecd/repo/call_conf_allocation/OutboundCallsRepo.java (1)

59-65: New CURRENT_TIMESTAMP predicate may require an index

Filtering by t.callDateTo >= CURRENT_TIMESTAMP was added to many JPQL queries.
Unless callDateTo is already indexed, every call list/count will trigger a full table scan – these methods are on hot paths (allocation dashboards). Verify there is a composite index starting with callDateTo.

Example migration (PostgreSQL):

CREATE INDEX idx_outbound_calls_callDateTo ON outbound_calls(call_date_to);
src/main/java/com/iemr/ecd/controller/reports/ReportController.java (1)

33-34: Import list still contains unused MediaType after CORS refactor

MediaType is required, but ensure any now-unused imports (e.g. @CrossOrigin) were fully removed to keep warnings at zero. Otherwise, controller logic remains untouched.

src/main/java/com/iemr/ecd/utils/mapper/JwtUserIdValidationFilter.java (2)

49-54: Pre-flight path: terminate the response cleanly

After setting status 200 on an OPTIONS request you should also:

  1. Explicitly flush/commit the response to ensure headers are sent.
  2. Consider returning after writing CORS headers (already done) but before any body; adding a return immediately after flushBuffer() avoids accidental fall-through if future code is appended.
if ("OPTIONS".equalsIgnoreCase(request.getMethod())) {
     logger.info("OPTIONS request - skipping JWT validation");
     response.setStatus(HttpServletResponse.SC_OK);
+    response.flushBuffer();
     return;
 }

131-148: isOriginAllowed is re-evaluated per request – pre-compile patterns

Splitting and building regexes on every call is O(N) string work per request and allocates many temporary objects.
Move the compilation to the constructor and reuse Patterns:

- private final String allowedOrigins;
+ private final List<Pattern> allowedOriginPatterns;

 public JwtUserIdValidationFilter(JwtAuthenticationUtil jwtAuthenticationUtil,
-        String allowedOrigins) {
+        String allowedOrigins) {
     this.jwtAuthenticationUtil = jwtAuthenticationUtil;
-    this.allowedOrigins = allowedOrigins;
+    this.allowedOriginPatterns = Arrays.stream(
+            Optional.ofNullable(allowedOrigins).orElse("")
+                    .split(","))
+        .map(String::trim)
+        .filter(s -> !s.isEmpty())
+        .map(JwtUserIdValidationFilter::toRegex)
+        .map(Pattern::compile)
+        .toList();
 }
 ...
-private boolean isOriginAllowed(String origin) {
-    if (origin == null || allowedOrigins == null || allowedOrigins.trim().isEmpty()) {
+private boolean isOriginAllowed(String origin) {
+    if (origin == null || allowedOriginPatterns.isEmpty()) {
         logger.warn("No allowed origins configured or origin is null");
         return false;
     }
-    return Arrays.stream(allowedOrigins.split(","))
-            .map(String::trim)
-            .anyMatch(pattern -> origin.matches(wildcardToRegex(pattern)));
+    return allowedOriginPatterns.stream()
+            .anyMatch(p -> p.matcher(origin).matches());
 }

Besides performance, compiling once avoids subtle regex-escaping errors that can creep in during the ad-hoc replace chain.

πŸ“œ Review details

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

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 260c238 and 3e350ec.

πŸ“’ Files selected for processing (26)
  • src/main/environment/ecd_ci.properties (1 hunks)
  • src/main/environment/ecd_example.properties (1 hunks)
  • src/main/java/com/iemr/ecd/config/WebConfiguration.java (1 hunks)
  • src/main/java/com/iemr/ecd/controller/associate/AutoPreviewDialingController.java (1 hunks)
  • src/main/java/com/iemr/ecd/controller/associate/BeneficiaryCallHistoryController.java (1 hunks)
  • src/main/java/com/iemr/ecd/controller/associate/BeneficiaryRegistrationController.java (1 hunks)
  • src/main/java/com/iemr/ecd/controller/associate/CallClosureController.java (1 hunks)
  • src/main/java/com/iemr/ecd/controller/callallocation/CallAllocationController.java (4 hunks)
  • src/main/java/com/iemr/ecd/controller/callallocation/CallConfigurationController.java (1 hunks)
  • src/main/java/com/iemr/ecd/controller/dataupload/DataTemplateController.java (1 hunks)
  • src/main/java/com/iemr/ecd/controller/dataupload/DataUploadController.java (1 hunks)
  • src/main/java/com/iemr/ecd/controller/masters/MastersController.java (2 hunks)
  • src/main/java/com/iemr/ecd/controller/outboundworklist/CallStatisticsController.java (1 hunks)
  • src/main/java/com/iemr/ecd/controller/outboundworklist/OutBoundWorklistController.java (2 hunks)
  • src/main/java/com/iemr/ecd/controller/quality/AgentQualityAuditorMappingController.java (1 hunks)
  • src/main/java/com/iemr/ecd/controller/quality/ChartsController.java (1 hunks)
  • src/main/java/com/iemr/ecd/controller/quality/GradeConfigurationController.java (1 hunks)
  • src/main/java/com/iemr/ecd/controller/quality/QualityAuditController.java (4 hunks)
  • src/main/java/com/iemr/ecd/controller/quality/QualityAuditQuestionConfigurationController.java (1 hunks)
  • src/main/java/com/iemr/ecd/controller/quality/QualityAuditSectionConfigurationController.java (1 hunks)
  • src/main/java/com/iemr/ecd/controller/quality/SampleSelectionConfigurationController.java (1 hunks)
  • src/main/java/com/iemr/ecd/controller/questionare/EcdQuestionareController.java (6 hunks)
  • src/main/java/com/iemr/ecd/controller/reports/ReportController.java (1 hunks)
  • src/main/java/com/iemr/ecd/repo/call_conf_allocation/OutboundCallsRepo.java (2 hunks)
  • src/main/java/com/iemr/ecd/utils/mapper/FilterConfig.java (1 hunks)
  • src/main/java/com/iemr/ecd/utils/mapper/JwtUserIdValidationFilter.java (3 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (3)
src/main/java/com/iemr/ecd/utils/mapper/FilterConfig.java (1)
src/main/java/com/iemr/ecd/config/WebConfiguration.java (1)
  • Configuration (32-56)
src/main/java/com/iemr/ecd/config/WebConfiguration.java (1)
src/main/java/com/iemr/ecd/utils/mapper/FilterConfig.java (1)
  • Configuration (9-28)
src/main/java/com/iemr/ecd/utils/mapper/JwtUserIdValidationFilter.java (1)
src/main/java/com/iemr/ecd/utils/constants/Constants.java (1)
  • Constants (5-24)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyze (java)
πŸ”‡ Additional comments (15)
src/main/java/com/iemr/ecd/controller/callallocation/CallConfigurationController.java (1)

30-38: Import cleanup is correct – controller no longer depends on @CrossOrigin.
Compilation path stays green and supports the new global CORS strategy.

src/main/java/com/iemr/ecd/controller/dataupload/DataUploadController.java (1)

28-33: Good removal of per-controller CORS annotation.
No functional side-effects detected; the controller now relies on the centralised WebConfiguration.

src/main/java/com/iemr/ecd/controller/quality/GradeConfigurationController.java (1)

30-37: Per-controller CORS annotation successfully dropped.
Nothing else changed in the controller logic – looks good.

src/main/java/com/iemr/ecd/controller/outboundworklist/CallStatisticsController.java (1)

28-33: CORS annotation removal aligns with new global policy.
Implementation remains unaffected.

src/main/environment/ecd_ci.properties (1)

32-33: Ensure the placeholder is resolved at deploy time.
If the @CORS_ALLOWED_ORIGINS@ token is not replaced by the CI pipeline, Spring will read it literally, effectively blocking every origin. Please verify that:

  1. The build system filters this file and injects the real value, or
  2. A default value is supplied via SPRING_APPLICATION_JSON / --cors.allowed-origins= at runtime.

Otherwise all browsers will receive CORS 403 responses.

src/main/java/com/iemr/ecd/controller/associate/BeneficiaryCallHistoryController.java (1)

28-28: Removed redundant @CrossOrigin import and annotation
The per-controller CORS annotation has been deleted to centralize CORS settings. Ensure your global WebConfiguration covers this endpoint so that CORS requests still succeed.

src/main/java/com/iemr/ecd/controller/associate/CallClosureController.java (1)

28-28: Removed controller‐level CORS annotation
Good removal of the CrossOrigin importβ€”CORS is now handled globally. Verify that /closure/closeCall is accessible from the intended origins via the new filter/config setup.

src/main/java/com/iemr/ecd/controller/quality/QualityAuditSectionConfigurationController.java (1)

30-30: Centralized CORS: drop @CrossOrigin
The CrossOrigin import was removed to rely on the global policy. Confirm that your cors.allowed-origins covers /sectionConfiguration routes in all deployment environments.

src/main/java/com/iemr/ecd/controller/quality/QualityAuditQuestionConfigurationController.java (1)

30-30: Removed per-controller CORS configuration
Nice cleanupβ€”controller is leaner without @CrossOrigin. Please validate that frontend apps can still call /questionnaireConfiguration under the centralized CORS policy.

src/main/java/com/iemr/ecd/controller/quality/SampleSelectionConfigurationController.java (1)

45-51: ```shell
#!/bin/bash

1. Check for any remaining @crossorigin annotations

rg -n '@crossorigin' --glob '*.java'

2. Locate the WebConfiguration class

rg -l 'class WebConfiguration' -g '*.java'

3. Inspect its CORS setup (including allowedOrigins, allowedMethods, allowedHeaders, allowCredentials)

rg -n 'addCorsMappings' -g '*.java' -A10 -B2


</details>
<details>
<summary>src/main/java/com/iemr/ecd/controller/dataupload/DataTemplateController.java (1)</summary>

`32-34`: **Import list clean-up acknowledged**

The removal of `CrossOrigin` import aligns with the new centralised CORS configuration – good catch.

</details>
<details>
<summary>src/main/java/com/iemr/ecd/controller/associate/BeneficiaryRegistrationController.java (1)</summary>

`28-30`: **CORS annotation removed – verify global config allows `Authorization` header**

Now that CORS is centralised, ensure the new `WebConfiguration`’s `allowedHeaders` contains `Authorization`; otherwise pre-flight requests to these endpoints will fail.

</details>
<details>
<summary>src/main/java/com/iemr/ecd/utils/mapper/FilterConfig.java (1)</summary>

`12-25`: ```shell
#!/bin/bash
set -e

echo "Locating JwtUserIdValidationFilter class..."
rg "class.*JwtUserIdValidationFilter" -n

echo -e "\nIdentifying source file path..."
FILTER_FILE=$(rg -l "class.*JwtUserIdValidationFilter" -n)

echo -e "\nShowing first 200 lines of the filter implementation:"
sed -n '1,200p' "$FILTER_FILE"

echo -e "\nSearching for CORS header manipulation in the filter:"
grep -R "Access-Control" -n "$(dirname "$FILTER_FILE")"
src/main/java/com/iemr/ecd/repo/call_conf_allocation/OutboundCallsRepo.java (1)

92-97: Inconsistent date-range criteria for MO flow

getMotherRecordsForMO now only applies callDateTo >= CURRENT_TIMESTAMP, whereas the ANM/Associate equivalents still constrain by (:fDate between …) OR (:tDate between …).

Was the omission intentional?
If not, the MO list will ignore the selected date window and may return records far outside the UI filter.

src/main/java/com/iemr/ecd/controller/questionare/EcdQuestionareController.java (1)

30-38: Unused import cleanup acknowledged

The @CrossOrigin import removal is consistent with project-wide CORS centralisation; nothing else changed. πŸ‘

vanitha1822
vanitha1822 previously approved these changes Jun 17, 2025
@sonarqubecloud
Copy link

@vishwab1 vishwab1 requested review from drtechie and vanitha1822 June 17, 2025 16:15
@vishwab1 vishwab1 merged commit 6ab7b18 into develop Jun 18, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants