Regex utils improvement

[andrewjschuang]

WHY

Summary by CodeRabbit

• New Features

  • Enhanced extraction functionality now supports configuring multiple sets of inputs, regular expressions, and output keys, allowing for more flexible and dynamic extraction workflows.

• Refactor

  • Improved the user interface for configuring extraction rules, making it easier to manage multiple extraction patterns.

• Chores

  • Updated the component and package versions to reflect recent changes.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)			Jun 9, 2025 9:18pm
pipedream-docs	⬜️ Ignored (Inspect)			Jun 9, 2025 9:18pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Jun 9, 2025 9:18pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The extract-by-regular-expressions-list action was refactored to support dynamic sets of input, regex, and output keys, allowing multiple extraction configurations. The logic was modularized, removing static properties and methods, and the result structure was updated to map keys to their respective match arrays. Package versions were incremented accordingly.

Changes

File(s)	Change Summary
components/pipedream_utils/actions/extract-by-regular-expressions-list/...	Refactored to support dynamic input/regex/key sets; modularized methods; updated result structure; version bump to 0.1.0
components/pipedream_utils/package.json	Incremented package version from 0.0.5 to 0.0.6

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Action
    loop For each defined key_n/input_n/regex_n group
        User->>Action: Provide key_n, input_n, regex_n
        Action->>Action: Parse regex_n
        Action->>Action: Extract matches from input_n
        Action->>Action: Store matches under key_n
    end
    Action-->>User: Return map of key_n to match arrays

Loading

Poem

In regex fields where patterns play,
The action now can parse all day.
Dynamic keys, inputs anew,
Each match returned, precise and true.
With version bumps, we hop ahead—
Regex rabbits, well regexed and well fed!
🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

components/pipedream_utils/actions/extract-by-regular-expressions-list/extract-by-regular-expressions-list.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:799:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:723:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:706:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:307:38)
at #link (node:internal/modules/esm/module_job:170:49)

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b668e70 and 8fd39dc.

📒 Files selected for processing (2)

• components/pipedream_utils/actions/extract-by-regular-expressions-list/extract-by-regular-expressions-list.mjs (1 hunks)
• components/pipedream_utils/package.json (1 hunks)

✨ 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

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