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

fix(app-sys): update regex for contentful namespaces #17783

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jonnigs
Copy link
Member

@jonnigs jonnigs commented Feb 3, 2025

What

Allow custom zod validation messages for nested applications

Why

The regex for the namespace in contentfull didn't match to applications in nested folders, like aosh

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
    • Enhanced namespace input validation to recognize a broader range of valid formats, including multiple dot-separated segments, ensuring that valid entries are correctly accepted.

Copy link
Contributor

coderabbitai bot commented Feb 3, 2025

Walkthrough

The changes modify the namespace validation in the populateError function by updating the regular expression. The regex is changed from /^\w*\.\w*:.*/g to /^[\w.]+:\w+(\.\w+)*$/g to support multiple dot-separated segments before the colon. There are no modifications to error handling, exported declarations, or other parts of the code.

Changes

File(s) Change Summary
libs/.../validators.ts Updated regex in the populateError function from /^\w*\.\w*:.*/g to /^[\w.]+:\w+(\.\w+)*$/g.

Possibly related PRs

Suggested labels

automerge, high priority

Suggested reviewers

  • HjorturJ
  • robertaandersen
✨ 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
🪧 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.

@jonnigs jonnigs marked this pull request as ready for review February 3, 2025 11:14
@jonnigs jonnigs requested a review from a team as a code owner February 3, 2025 11:14
Copy link

nx-cloud bot commented Feb 3, 2025

View your CI Pipeline Execution ↗ for commit 2301b99.

Command Status Duration Result
nx run-many --projects application-system-api -... ✅ Succeeded 16m 31s View ↗
nx run-many --projects application-api-core,app... ✅ Succeeded 9m 6s View ↗
nx run-many --target=build --projects=api --par... ✅ Succeeded 6m 15s View ↗
nx run-many --target=build --projects=applicati... ✅ Succeeded 5m 5s View ↗
nx run-many --projects api,api-domains-applicat... ✅ Succeeded 12s View ↗
nx run-many --target=codegen/frontend-client --... ✅ Succeeded 13s View ↗
nx run-many --target=codegen/backend-schema --a... ✅ Succeeded 21s View ↗
nx run-many --target=build --projects=applicati... ✅ Succeeded 2m 44s View ↗
Additional runs (9) ✅ Succeeded ... View ↗

☁️ Nx Cloud last updated this comment at 2025-02-03 11:52:34 UTC

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: 1

🧹 Nitpick comments (1)
libs/application/core/src/validation/validators.ts (1)

30-30: Consider a more specific regex pattern.

While the current pattern works, we could make it more specific to prevent potential misuse.

Consider this alternative pattern that enforces stricter rules:

-      const namespaceRegex = /^[\w.]+:\w+(\.\w+)*$/g
+      const namespaceRegex = /^[a-z][\w]*(?:\.[a-z][\w]*)*:[a-z][\w]*(?:\.[a-z][\w]*)*$/g

This pattern:

  • Enforces segments to start with lowercase letters
  • Maintains camelCase convention
  • Prevents consecutive dots
  • Ensures cleaner namespace structure
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 51fc50e and 2301b99.

📒 Files selected for processing (1)
  • libs/application/core/src/validation/validators.ts (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
libs/application/core/src/validation/validators.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."
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: prepare

@jonnigs jonnigs enabled auto-merge February 3, 2025 12:09
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.

2 participants