Fix spelling#20077
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
dannyroosevelt
moved this to Ready for PR Review
in Component (Source and Action) Backlog
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughWidespread patch-level version bumps and string/typo fixes across many components, actions, sources, and package manifests. Changes are limited to metadata, exported version fields, labels, descriptions, JSDoc comments, and a few renamed properties; no control-flow or behavioral logic changes. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment |
Collaborator
|
Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified. |
Collaborator
michelle0927
moved this from Ready for PR Review
to In Review
in Component (Source and Action) Backlog
michelle0927
moved this from In Review
to Doing
in Component (Source and Action) Backlog
verhovsky
commented
Feb 20, 2026
verhovsky
commented
Feb 20, 2026
verhovsky
commented
Feb 20, 2026
verhovsky
marked this pull request as ready for review
February 26, 2026 00:42
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 15
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (12)
components/stiply/actions/send-sign-request/send-sign-request.mjs (1)
95-95:⚠️ Potential issue | 🟡 MinorTypo in summary message: semicolon instead of colon.
Since this PR focuses on spelling fixes, consider also correcting the punctuation here: "ID;" should be "ID:".
✏️ Proposed fix
- $.export("$summary", `Sign request with ID; ${response.data.id} sent successfully`); + $.export("$summary", `Sign request with ID: ${response.data.id} sent successfully`);🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@components/stiply/actions/send-sign-request/send-sign-request.mjs` at line 95, Change the punctuation in the summary export so it uses a colon instead of a semicolon: update the $.export("$summary", `Sign request with ID; ${response.data.id} sent successfully`) statement in send-sign-request.mjs to read "ID:" so the summary becomes "Sign request with ID: {id} sent successfully".components/quentn/actions/run-campaign-for-contact/run-campaign-for-contact.mjs (2)
59-64:⚠️ Potential issue | 🟡 MinorPotential TypeError if
error.responseis undefined.Accessing
error.response.statuswill throw iferror.responseis undefined, which can occur for network errors or non-HTTP failures.Proposed fix with optional chaining
} catch (error) { - if (error.response.status === 404) { + if (error.response?.status === 404) { throw new Error("Campaign not found"); } throw error; }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@components/quentn/actions/run-campaign-for-contact/run-campaign-for-contact.mjs` around lines 59 - 64, In the catch block inside run-campaign-for-contact.mjs (the code that currently checks error.response.status === 404), guard against undefined response by using optional chaining or an explicit check — e.g. change the condition to if (error?.response?.status === 404) (or if (error.response && error.response.status === 404)) so network/non-HTTP errors won't throw a TypeError; keep the same throw new Error("Campaign not found") and rethrow otherwise.
30-30:⚠️ Potential issue | 🟡 MinorInconsistent spelling: method name still contains the typo.
The label was fixed from "Receieve" to "Receive", but the method name
triggerAPIRecieveElementstill has the same misspelling. Since this PR is about spelling fixes, consider renaming the method for consistency.Proposed fix
- triggerAPIRecieveElement({ + triggerAPIReceiveElement({And update the call site on line 48:
- const response = await this.triggerAPIRecieveElement({ + const response = await this.triggerAPIReceiveElement({🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@components/quentn/actions/run-campaign-for-contact/run-campaign-for-contact.mjs` at line 30, The function name triggerAPIRecieveElement still uses the typo "Recieve"; rename the function to triggerAPIReceiveElement and update all usages (including the call in run-campaign-for-contact where triggerAPIRecieveElement is invoked) to the new name to keep spelling consistent across declaration and call sites; ensure any exports/imports, tests, or references that use triggerAPIRecieveElement are updated to triggerAPIReceiveElement to avoid broken references.components/quaderno/actions/create-contact/create-contact.mjs (1)
96-100:⚠️ Potential issue | 🟡 MinorRemaining typo in department description.
Line 99 still has a spelling error (
deparment→department), so the spelling cleanup in this block is incomplete.✏️ Proposed fix
- description: "If the contact is a `company`, this is the deparment.", + description: "If the contact is a `company`, this is the department.",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@components/quaderno/actions/create-contact/create-contact.mjs` around lines 96 - 100, The description string for the department field in the create-contact action still contains a typo; update the description in the department property (the object with key "department" in components/quaderno/actions/create-contact/create-contact.mjs) to replace "deparment" with "department" so it reads "If the contact is a `company`, this is the department."components/microsoft_outlook/actions/find-shared-folder-email/find-shared-folder-email.mjs (1)
87-87: 🧹 Nitpick | 🔵 TrivialConsider using strict inequality for consistency.
Use
!==instead of!=to follow JavaScript best practices and avoid potential type coercion issues.🔧 Optional improvement
- $.export("$summary", `Successfully retrieved ${emails.length} shared folder message${emails.length != 1 + $.export("$summary", `Successfully retrieved ${emails.length} shared folder message${emails.length !== 1 ? "s" : ""}.`);🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@components/microsoft_outlook/actions/find-shared-folder-email/find-shared-folder-email.mjs` at line 87, Replace the non-strict inequality in the summary template to avoid type coercion: change the expression using emails.length != 1 to use strict inequality (emails.length !== 1) in the $.export("$summary", ...) template so the pluralization check in the find-shared-folder-email action is consistent and safe.components/microsoft_outlook/actions/find-email/find-email.mjs (1)
89-91: 🧹 Nitpick | 🔵 TrivialConsider using strict equality.
The code uses loose equality (
!=) instead of strict equality (!==). While this works correctly here, using strict equality is generally preferred in JavaScript for consistency and to avoid type coercion issues.♻️ Suggested improvement
- $.export("$summary", `Successfully retrieved ${emails.length} message${emails.length != 1 + $.export("$summary", `Successfully retrieved ${emails.length} message${emails.length !== 1 ? "s" : ""}.`);🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@components/microsoft_outlook/actions/find-email/find-email.mjs` around lines 89 - 91, Update the pluralization check in the export summary to use strict equality: replace the loose comparison emails.length != 1 with emails.length !== 1 in the $.export(...) expression so the message logic remains the same but uses strict equality; the change should be applied where $.export("$summary", `Successfully retrieved ${emails.length} message${emails.length != 1 ? "s" : ""}.`); is defined.components/wordpress_com/actions/upload-media/upload-media.mjs (1)
59-65:⚠️ Potential issue | 🟡 MinorMisleading comment contradicts the logic.
The comment on line 59 states "If not form data", but the condition
if (wordpress.isFormData(media))actually checks if the media is FormData. The logic is correct (when media is FormData, use it directly; otherwise, prepare it), but the comment creates confusion.📝 Proposed fix to correct the comment
- // If not form data + // If already form data if (wordpress.isFormData(media)) { form = media;🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@components/wordpress_com/actions/upload-media/upload-media.mjs` around lines 59 - 65, The inline comment is reversed and misleading: update the comment above the if statement that uses wordpress.isFormData(media) so it accurately reflects the logic (i.e., "If media is FormData, use it directly; otherwise prepare it"), leaving the condition and branches (wordpress.isFormData(media), form = media, else form = await prepareMediaUpload(media, fields, $)) unchanged; reference the check in upload-media.mjs and the prepareMediaUpload helper to locate where to amend the comment.components/reddit/sources/new-comments-on-a-post/new-comments-on-a-post.mjs (1)
33-33: 🧹 Nitpick | 🔵 TrivialConsider using a more user-friendly label.
The label uses camelCase
"numberOfParents"which is less readable in UIs. Consider using a space-separated format for better user experience.🎨 Proposed label improvement
- label: "numberOfParents", + label: "Number of Parents",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@components/reddit/sources/new-comments-on-a-post/new-comments-on-a-post.mjs` at line 33, Update the user-facing label for the field currently defined as label: "numberOfParents" to a more readable, space-separated string (e.g., "Number of parents" or "Number of Parents") so UIs render a friendlier name; locate the label property for the relevant field in the new-comments-on-a-post source (the label key named "numberOfParents") and replace the camelCase string with the chosen human-readable phrase.components/mailchimp/sources/new-or-updated-list-segment/new-or-updated-list-segment.mjs (1)
87-89: 🧹 Nitpick | 🔵 TrivialRemove redundant assignment in ternary expression.
The ternary expression contains unnecessary double assignments (
segments = segments = await...) in both branches. This reduces code clarity.♻️ Simplify by removing redundant assignments
segments = this.watchFor === "Created" - ? segments = await this.mailchimp.getAudienceSegmentsByCreatedDate(this.listId, config) - : segments = await this.mailchimp.getAudienceSegmentsByUpdatedDate(this.listId, config); + ? await this.mailchimp.getAudienceSegmentsByCreatedDate(this.listId, config) + : await this.mailchimp.getAudienceSegmentsByUpdatedDate(this.listId, config);🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@components/mailchimp/sources/new-or-updated-list-segment/new-or-updated-list-segment.mjs` around lines 87 - 89, The ternary currently does a redundant double assignment to segments; simplify the assignment by assigning once: set segments = this.watchFor === "Created" ? await this.mailchimp.getAudienceSegmentsByCreatedDate(this.listId, config) : await this.mailchimp.getAudienceSegmentsByUpdatedDate(this.listId, config). This removes the extra `segments =` in both branches and keeps behavior identical (references: variable `segments`, `this.watchFor`, `getAudienceSegmentsByCreatedDate`, `getAudienceSegmentsByUpdatedDate`, `this.listId`, `config`).components/mailchimp/actions/edit-campaign-template-content/edit-campaign-template-content.mjs (1)
46-51:⚠️ Potential issue | 🟡 MinorFix incorrect label and description for the
htmlprop.The
htmlprop has the label "Plain text" and a description about plain-text content, which appears to be copied from theplainTextprop above (lines 42-45). This will confuse users about the prop's purpose.📝 Proposed fix
html: { type: "string", - label: "Plain text", - description: "The plain-text portion of the campaign. If left unspecified, we'll generate this automatically.", + label: "HTML", + description: "The HTML content of the campaign. If left unspecified, we'll generate this automatically.", optional: true, },🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@components/mailchimp/actions/edit-campaign-template-content/edit-campaign-template-content.mjs` around lines 46 - 51, The html prop currently has the wrong label/description (it says "Plain text"); update the html property definition in edit-campaign-template-content.mjs (the object key named html) so its label and description correctly describe HTML content—e.g., set label to "HTML" or "HTML content" and description to "The HTML portion of the campaign; if left unspecified, we'll generate this automatically." Leave other attributes (type, optional) unchanged.components/click2mail2/package.json (1)
18-18: 🧹 Nitpick | 🔵 TrivialPre-existing issue:
fsshould not be listed as a dependency.The
fsmodule is a built-in Node.js module and should not be added topackage.jsondependencies. The npm packagefs@0.0.1-securityis a placeholder that provides no functionality. Consider removing this in a follow-up PR.Based on learnings: "When developing Pipedream components, do not add built-in Node.js modules like
fstopackage.jsondependencies, as they are native modules provided by the Node.js runtime."Proposed fix (for a follow-up PR)
"dependencies": { "@pipedream/platform": "^3.1.1", - "form-data": "^4.0.4", - "fs": "^0.0.1-security" + "form-data": "^4.0.4" }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@components/click2mail2/package.json` at line 18, Remove the incorrect dependency entry for the built-in Node.js module "fs" from package.json (the line with "fs": "^0.0.1-security"); this package is a placeholder and should not be listed as a dependency—delete that dependency key from the dependencies object so the component relies on the runtime-provided fs instead.components/xero_accounting_api/actions/xero-accounting-update-contact/xero-accounting-update-contact.mjs (1)
158-176:⚠️ Potential issue | 🟠 MajorProp renames are breaking changes for existing users.
The typo fixes in
puchasesDefaultAccountCode→purchasesDefaultAccountCodeandpuechasesTrackingCategories→purchasesTrackingCategoriesare correct, but renaming props breaks backward compatibility. Existing workflows using the old property names will lose their saved values after this update.Consider whether this warrants:
- A migration strategy to preserve existing user data
- Documentation as a breaking change
- A major version bump instead of the current patch version
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@components/xero_accounting_api/actions/xero-accounting-update-contact/xero-accounting-update-contact.mjs` around lines 158 - 176, Keep backwards compatibility by accepting the old misspelled property names as aliases while retaining the corrected names; update the action input handling to map incoming puchasesDefaultAccountCode -> purchasesDefaultAccountCode and puechasesTrackingCategories -> purchasesTrackingCategories (so both spellings are supported), and add a deprecation warning (via logger or metadata) when the old names are used. Modify the input normalization logic where these fields are read (look for purchasesDefaultAccountCode, salesTrackingCategories, purchasesTrackingCategories in the action handler) to perform the fallback mapping and emit the deprecation notice; do not remove the corrected property names so existing saved values and new correct usage both work.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@components/boloforms/actions/send-template-signature/send-template-signature.mjs`:
- Line 48: Update the description string for the customVariables property in
send-template-signature.mjs to fix the comma splice: change the clause "If you
don't pass customVariables then the call will still work, Boloforms will pass
each variable as empty" to use a semicolon or split into two sentences (e.g.
"...still work; Boloforms will pass..." or "...still work. Boloforms will
pass...") so the description assigned to the description field is grammatically
correct.
In `@components/github/sources/new-gist/new-gist.mjs`:
- Around line 7-8: The documentation URL in the description string of
new-gist.mjs contains a malformed apiVersion query parameter
("apiVersion=20.2.61-28"); update that query parameter to the correct date-based
GitHub API version "apiVersion=2022-11-28" inside the description value so the
link follows GitHub's YYYY-MM-DD format (locate the description property in the
new-gist.mjs module and replace the apiVersion value in the URL).
In `@components/heyy/package.json`:
- Line 3: Add a CHANGELOG.md file in the components/heyy directory documenting
the release for package.json's bumped version "0.1.3"; create an entry that
follows the project's format, e.g., a header "## [0.1.3] - YYYY-MM-DD" followed
by a "### Added/Changed/Fixed" section and at least one bullet describing the
changes included in this release (use the actual release date and concise change
description).
In `@components/kanban_tool/package.json`:
- Line 3: The package.json version was unintentionally downgraded from 0.0.2 to
0.0.1; update the "version" field in components/kanban_tool/package.json to the
intended next patch (0.0.3) to keep versions monotonically increasing and avoid
npm publish/dependency issues, and ensure the change aligns with any release
tag/changelog entries and other package version bumps in this PR.
In `@components/line/sources/new-message-received/new-message-received.mjs`:
- Line 9: The commit only changes the version field "version: \"0.0.3\"" in
new-message-received.mjs; either revert that line back to "0.0.2" if there are
no functional changes, or add a corresponding CHANGELOG.md entry in the line
component directory documenting what justifies the bump; update the same file's
version string accordingly and ensure the new CHANGELOG.md contains a short
entry referencing the component name and the 0.0.3 change.
In
`@components/mailchimp/actions/edit-campaign-template-content/edit-campaign-template-content.mjs`:
- Line 11: Update the 'html' prop metadata for the action: find the html
property definition (the object with key "html") and change its label from
"Plain text" to "HTML" and update the description to refer to the HTML portion
of the campaign (e.g., "The HTML portion of the campaign. If left unspecified,
we'll generate this automatically."); keep the type and optional flag as-is so
only the label and description are corrected.
In `@components/mailchimp/actions/get-campaign-report/get-campaign-report.mjs`:
- Around line 7-10: The component key value "mailchimp-get-a-campaign-report" in
the exported manifest should match the folder/file slug "get-campaign-report";
update the exported key property (the one currently set to
"mailchimp-get-a-campaign-report") to "mailchimp-get-campaign-report" so the key
and the folder/file name (get-campaign-report) align and clear the pipeline
warning.
In `@components/neon_postgres/sources/new-or-updated-row/new-or-updated-row.mjs`:
- Line 38: Update the description string in new-or-updated-row.mjs: replace the
article "an" before "unique" with "a" so the description property reads
logically (e.g., the description field for the new-or-updated-row source should
be "The column to identify a unique row, commonly its `id` or `uuid`."); locate
the description property in the module to make this one-word change.
In `@components/paigo/package.json`:
- Line 3: Create components/paigo/CHANGELOG.md and add a new "0.1.1" entry
matching the package.json bump; include the version header (0.1.1), release date
(today's date or YYYY-MM-DD), and a short bullet describing the change (spelling
fixes). Ensure the changelog is formatted consistently with other project
CHANGELOG.md files (e.g., Markdown headers and bullets) so it clearly
corresponds to the "version": "0.1.1" line in package.json.
In `@components/postgresql/sources/new-or-updated-row/new-or-updated-row.mjs`:
- Line 38: Update the description string for the "column to identify an unique
row" to use the correct article: change "an unique row" to "a unique row" in the
description property (the description field in new-or-updated-row.mjs where the
string "The column to identify an unique row, commonly its `id` or `uuid`."
appears); keep the earlier "it's" → "its" correction and ensure the final
description reads "The column to identify a unique row, commonly its `id` or
`uuid`."
In `@components/reddit/sources/new-comments-on-a-post/new-comments-on-a-post.mjs`:
- Line 11: Update the component description string to clearly state it's
monitoring a specific post rather than the whole subreddit: replace the current
description "Emit new event each time a new comment is added to a subreddit."
with "Emit new event each time a new comment is added to a post."; locate the
description in the "new-comments-on-a-post" component (look for the description
line near the component key and the subredditPost prop) and make the one-line
wording change.
In `@components/svix/package.json`:
- Line 3: Create a CHANGELOG.md for the svix component (or update the shared
changelog for this component family) that includes a top-level entry for version
0.0.3 to match the "version": "0.0.3" in package.json; add a heading like "##
0.0.3 - YYYY-MM-DD" and a short bullet list describing the changes included in
this bump (e.g., bug fixes, features, or dependency updates), then save it in
the components/svix directory (or the shared changelog location) so the
repository has a recorded changelog entry for 0.0.3.
In `@packages/browsers/package.json`:
- Line 4: The package description in the package.json contains a spelling
mistake: change the word "compatability" to "compatibility" in the description
field (the string value for "description") so it reads "Includes the prebuilt
binaries and specific versions for compatibility with Pipedream."; update only
the description string in package.json.
In `@scripts/gitpod_api_wizard.sh`:
- Line 41: The inline development testing comment in
scripts/gitpod_api_wizard.sh references a non-existent script name ("bash
setup.sh"); update that comment to either point to the correct script ("bash
scripts/gitpod_api_wizard.sh" or the current entrypoint used for testing) or
remove the stale instruction entirely. Locate the comment in
scripts/gitpod_api_wizard.sh (the line containing "To test for development: gp
env -u PD_API_KEY; bash setup.sh") and change the referenced script name to the
correct path or delete the line if the testing approach has changed so the
repository no longer points to a missing file.
- Line 37: Replace the blocking plain "read" after the printf with a single-key,
raw read to match the "Press any key" prompt: change the read invocation in the
printf/read line to use read -r -n1 -s (or equivalent flags) so it consumes a
single keypress without requiring Enter and avoids backslash mangling.
---
Outside diff comments:
In `@components/click2mail2/package.json`:
- Line 18: Remove the incorrect dependency entry for the built-in Node.js module
"fs" from package.json (the line with "fs": "^0.0.1-security"); this package is
a placeholder and should not be listed as a dependency—delete that dependency
key from the dependencies object so the component relies on the runtime-provided
fs instead.
In
`@components/mailchimp/actions/edit-campaign-template-content/edit-campaign-template-content.mjs`:
- Around line 46-51: The html prop currently has the wrong label/description (it
says "Plain text"); update the html property definition in
edit-campaign-template-content.mjs (the object key named html) so its label and
description correctly describe HTML content—e.g., set label to "HTML" or "HTML
content" and description to "The HTML portion of the campaign; if left
unspecified, we'll generate this automatically." Leave other attributes (type,
optional) unchanged.
In
`@components/mailchimp/sources/new-or-updated-list-segment/new-or-updated-list-segment.mjs`:
- Around line 87-89: The ternary currently does a redundant double assignment to
segments; simplify the assignment by assigning once: set segments =
this.watchFor === "Created" ? await
this.mailchimp.getAudienceSegmentsByCreatedDate(this.listId, config) : await
this.mailchimp.getAudienceSegmentsByUpdatedDate(this.listId, config). This
removes the extra `segments =` in both branches and keeps behavior identical
(references: variable `segments`, `this.watchFor`,
`getAudienceSegmentsByCreatedDate`, `getAudienceSegmentsByUpdatedDate`,
`this.listId`, `config`).
In `@components/microsoft_outlook/actions/find-email/find-email.mjs`:
- Around line 89-91: Update the pluralization check in the export summary to use
strict equality: replace the loose comparison emails.length != 1 with
emails.length !== 1 in the $.export(...) expression so the message logic remains
the same but uses strict equality; the change should be applied where
$.export("$summary", `Successfully retrieved ${emails.length}
message${emails.length != 1 ? "s" : ""}.`); is defined.
In
`@components/microsoft_outlook/actions/find-shared-folder-email/find-shared-folder-email.mjs`:
- Line 87: Replace the non-strict inequality in the summary template to avoid
type coercion: change the expression using emails.length != 1 to use strict
inequality (emails.length !== 1) in the $.export("$summary", ...) template so
the pluralization check in the find-shared-folder-email action is consistent and
safe.
In `@components/quaderno/actions/create-contact/create-contact.mjs`:
- Around line 96-100: The description string for the department field in the
create-contact action still contains a typo; update the description in the
department property (the object with key "department" in
components/quaderno/actions/create-contact/create-contact.mjs) to replace
"deparment" with "department" so it reads "If the contact is a `company`, this
is the department."
In
`@components/quentn/actions/run-campaign-for-contact/run-campaign-for-contact.mjs`:
- Around line 59-64: In the catch block inside run-campaign-for-contact.mjs (the
code that currently checks error.response.status === 404), guard against
undefined response by using optional chaining or an explicit check — e.g. change
the condition to if (error?.response?.status === 404) (or if (error.response &&
error.response.status === 404)) so network/non-HTTP errors won't throw a
TypeError; keep the same throw new Error("Campaign not found") and rethrow
otherwise.
- Line 30: The function name triggerAPIRecieveElement still uses the typo
"Recieve"; rename the function to triggerAPIReceiveElement and update all usages
(including the call in run-campaign-for-contact where triggerAPIRecieveElement
is invoked) to the new name to keep spelling consistent across declaration and
call sites; ensure any exports/imports, tests, or references that use
triggerAPIRecieveElement are updated to triggerAPIReceiveElement to avoid broken
references.
In `@components/reddit/sources/new-comments-on-a-post/new-comments-on-a-post.mjs`:
- Line 33: Update the user-facing label for the field currently defined as
label: "numberOfParents" to a more readable, space-separated string (e.g.,
"Number of parents" or "Number of Parents") so UIs render a friendlier name;
locate the label property for the relevant field in the new-comments-on-a-post
source (the label key named "numberOfParents") and replace the camelCase string
with the chosen human-readable phrase.
In `@components/stiply/actions/send-sign-request/send-sign-request.mjs`:
- Line 95: Change the punctuation in the summary export so it uses a colon
instead of a semicolon: update the $.export("$summary", `Sign request with ID;
${response.data.id} sent successfully`) statement in send-sign-request.mjs to
read "ID:" so the summary becomes "Sign request with ID: {id} sent
successfully".
In `@components/wordpress_com/actions/upload-media/upload-media.mjs`:
- Around line 59-65: The inline comment is reversed and misleading: update the
comment above the if statement that uses wordpress.isFormData(media) so it
accurately reflects the logic (i.e., "If media is FormData, use it directly;
otherwise prepare it"), leaving the condition and branches
(wordpress.isFormData(media), form = media, else form = await
prepareMediaUpload(media, fields, $)) unchanged; reference the check in
upload-media.mjs and the prepareMediaUpload helper to locate where to amend the
comment.
In
`@components/xero_accounting_api/actions/xero-accounting-update-contact/xero-accounting-update-contact.mjs`:
- Around line 158-176: Keep backwards compatibility by accepting the old
misspelled property names as aliases while retaining the corrected names; update
the action input handling to map incoming puchasesDefaultAccountCode ->
purchasesDefaultAccountCode and puechasesTrackingCategories ->
purchasesTrackingCategories (so both spellings are supported), and add a
deprecation warning (via logger or metadata) when the old names are used. Modify
the input normalization logic where these fields are read (look for
purchasesDefaultAccountCode, salesTrackingCategories,
purchasesTrackingCategories in the action handler) to perform the fallback
mapping and emit the deprecation notice; do not remove the corrected property
names so existing saved values and new correct usage both work.
ℹ️ Review info
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (241)
components/addressfinder/actions/verify-email/verify-email.mjscomponents/addressfinder/package.jsoncomponents/airmeet/actions/add-authorized-attendee/add-authorized-attendee.mjscomponents/airmeet/package.jsoncomponents/alpaca/actions/get-account-info/get-account-info.mjscomponents/alpaca/package.jsoncomponents/bandwidth/actions/send-sms/send-sms.jscomponents/bandwidth/bandwidth.app.jscomponents/bandwidth/package.jsoncomponents/bandwidth/sources/new-incoming-sms/new-incoming-sms.jscomponents/bandwidth/sources/new-outgoing-sms/new-outgoing-sms.jscomponents/bloomerang/actions/add-interaction/add-interaction.mjscomponents/bloomerang/package.jsoncomponents/bluesky/actions/create-post/create-post.mjscomponents/bluesky/actions/like-post/like-post.mjscomponents/bluesky/actions/retrieve-thread/retrieve-thread.mjscomponents/bluesky/common/constants.mjscomponents/bluesky/package.jsoncomponents/bluesky/sources/new-follower-on-account/new-follower-on-account.mjscomponents/bluesky/sources/new-posts-by-author/new-posts-by-author.mjscomponents/bluesky/sources/new-timeline-posts/new-timeline-posts.mjscomponents/boloforms/actions/send-template-signature/send-template-signature.mjscomponents/boloforms/package.jsoncomponents/clerk/actions/create-user/create-user.mjscomponents/clerk/package.jsoncomponents/click2mail2/actions/create-job/create-job.mjscomponents/click2mail2/package.jsoncomponents/discord/README.mdcomponents/discord_bot/README.mdcomponents/dropbox/actions/download-file-to-tmp/download-file-to-tmp.mjscomponents/dropbox/package.jsoncomponents/firefish/actions/unsubscribe-email/unsubscribe-email.mjscomponents/firefish/package.jsoncomponents/freshdesk/package.jsoncomponents/freshdesk/sources/common/polling.mjscomponents/freshdesk/sources/contact-updated/contact-updated.mjscomponents/freshdesk/sources/new-contact/new-contact.mjscomponents/freshdesk/sources/new-ticket/new-ticket.mjscomponents/freshdesk/sources/ticket-updated/ticket-updated.mjscomponents/ghost_org_admin_api/package.jsoncomponents/ghost_org_admin_api/sources/common-webhook.mjscomponents/ghost_org_admin_api/sources/member-created/member-created.mjscomponents/ghost_org_admin_api/sources/member-deleted/member-deleted.mjscomponents/ghost_org_admin_api/sources/member-updated/member-updated.mjscomponents/ghost_org_admin_api/sources/new-tag/new-tag.mjscomponents/ghost_org_admin_api/sources/page-published/page-published.mjscomponents/ghost_org_admin_api/sources/post-published/post-published.mjscomponents/github/actions/common/utils.mjscomponents/github/actions/create-gist/create-gist.mjscomponents/github/actions/update-gist/update-gist.mjscomponents/github/package.jsoncomponents/github/sources/new-gist/new-gist.mjscomponents/goodbits/actions/update-subscriber-status/update-subscriber-status.mjscomponents/goodbits/package.jsoncomponents/google_dialogflow/actions/get-entity-type/get-entity-type.mjscomponents/google_dialogflow/actions/list-intents/list-intents.mjscomponents/google_dialogflow/package.jsoncomponents/google_recaptcha/actions/validate-recaptcha/validate-recaptcha.tscomponents/google_recaptcha/package.jsoncomponents/google_search_console/actions/retrieve-site-performance-data/retrieve-site-performance-data.mjscomponents/google_search_console/actions/submit-url-for-indexing/submit-url-for-indexing.mjscomponents/google_search_console/common/methods.mjscomponents/google_search_console/package.jsoncomponents/guru/README.mdcomponents/helpdocs/actions/list-articles/list-articles.mjscomponents/helpdocs/package.jsoncomponents/heyy/actions/send-whatsapp-message/send-whatsapp-message.mjscomponents/heyy/package.jsoncomponents/hubspot/package.jsoncomponents/hubspot/sources/new-engagement/new-engagement.mjscomponents/jumpseller/package.jsoncomponents/jumpseller/sources/order-updated/order-updated.mjscomponents/kanban_tool/actions/find-task/find-task.mjscomponents/kanban_tool/actions/get-task-details/get-task-details.mjscomponents/kanban_tool/package.jsoncomponents/klaviyo/README.mdcomponents/leiga/actions/create-issue/create-issue.mjscomponents/leiga/leiga.app.mjscomponents/leiga/package.jsoncomponents/leiga/sources/deleted-issue-instant/deleted-issue-instant.mjscomponents/leiga/sources/new-issue-instant/new-issue-instant.mjscomponents/leiga/sources/updated-issue-instant/updated-issue-instant.mjscomponents/line/actions/send-broadcast-message/send-broadcast-message.mjscomponents/line/actions/send-notification-message/send-notification-message.mjscomponents/line/actions/send-push-message/send-push-message.mjscomponents/line/actions/send-reply-message/send-reply-message.mjscomponents/line/line.app.mjscomponents/line/package.jsoncomponents/line/sources/new-message-received/new-message-received.mjscomponents/linkedin/actions/retrieve-comments-shares/retrieve-comments-shares.mjscomponents/linkedin/package.jsoncomponents/listen_notes/actions/full-search/full-search.mjscomponents/listen_notes/actions/get-episode-details/get-episode-details.mjscomponents/listen_notes/actions/get-podcast-details/get-podcast-details.mjscomponents/listen_notes/listen_notes.app.mjscomponents/listen_notes/package.jsoncomponents/mailchimp/actions/add-note-to-subscriber/add-note-to-subscriber.mjscomponents/mailchimp/actions/add-or-update-subscriber/add-or-update-subscriber.mjscomponents/mailchimp/actions/add-remove-member-tags/add-remove-member-tags.mjscomponents/mailchimp/actions/add-segment-member/add-segment-member.mjscomponents/mailchimp/actions/add-subscriber-to-tag/add-subscriber-to-tag.mjscomponents/mailchimp/actions/create-campaign/create-campaign.mjscomponents/mailchimp/actions/create-list/create-list.mjscomponents/mailchimp/actions/delete-campaign/delete-campaign.mjscomponents/mailchimp/actions/delete-list-member/delete-list-member.mjscomponents/mailchimp/actions/delete-list/delete-list.mjscomponents/mailchimp/actions/edit-campaign-template-content/edit-campaign-template-content.mjscomponents/mailchimp/actions/get-campaign-report/get-campaign-report.mjscomponents/mailchimp/actions/get-campaign/get-campaign.mjscomponents/mailchimp/actions/get-list-activities/get-list-activities.mjscomponents/mailchimp/actions/get-list-member-activity/get-list-member-activity.mjscomponents/mailchimp/actions/get-list-member-tags/get-list-member-tags.mjscomponents/mailchimp/actions/get-list/get-list.mjscomponents/mailchimp/actions/list-segment-member/list-segment-member.mjscomponents/mailchimp/actions/remove-segment-member/remove-segment-member.mjscomponents/mailchimp/actions/search-campaign/search-campaign.mjscomponents/mailchimp/actions/search-lists/search-lists.mjscomponents/mailchimp/actions/search-member/search-member.mjscomponents/mailchimp/actions/send-campaign/send-campaign.mjscomponents/mailchimp/actions/unsubscribe-email/unsubscribe-email.mjscomponents/mailchimp/actions/update-campaign/update-campaign.mjscomponents/mailchimp/actions/update-list/update-list.mjscomponents/mailchimp/mailchimp.app.mjscomponents/mailchimp/package.jsoncomponents/mailchimp/sources/link-clicked/link-clicked.mjscomponents/mailchimp/sources/new-audience/new-audience.mjscomponents/mailchimp/sources/new-campaign/new-campaign.mjscomponents/mailchimp/sources/new-customer/new-customer.mjscomponents/mailchimp/sources/new-file/new-file.mjscomponents/mailchimp/sources/new-list-event/new-list-event.mjscomponents/mailchimp/sources/new-open/new-open.mjscomponents/mailchimp/sources/new-or-updated-list-segment/new-or-updated-list-segment.mjscomponents/mailchimp/sources/new-or-updated-subscriber/new-or-updated-subscriber.mjscomponents/mailchimp/sources/new-order/new-order.mjscomponents/mailchimp/sources/new-segment-tag-subscriber/new-segment-tag-subscriber.mjscomponents/mailchimp/sources/new-subscriber/new-subscriber.mjscomponents/mailchimp/sources/new-unsubscriber/new-unsubscriber.mjscomponents/mailwizz/actions/create-campaign/create-campaign.mjscomponents/mailwizz/package.jsoncomponents/microsoft_onedrive/actions/get-file-by-id/get-file-by-id.mjscomponents/microsoft_onedrive/package.jsoncomponents/microsoft_outlook/actions/add-label-to-email/add-label-to-email.mjscomponents/microsoft_outlook/actions/approve-workflow/approve-workflow.mjscomponents/microsoft_outlook/actions/create-contact/create-contact.mjscomponents/microsoft_outlook/actions/create-draft-email/create-draft-email.mjscomponents/microsoft_outlook/actions/download-attachment/download-attachment.mjscomponents/microsoft_outlook/actions/find-contacts/find-contacts.mjscomponents/microsoft_outlook/actions/find-email/find-email.mjscomponents/microsoft_outlook/actions/find-shared-folder-email/find-shared-folder-email.mjscomponents/microsoft_outlook/actions/list-contacts/list-contacts.mjscomponents/microsoft_outlook/actions/list-folders/list-folders.mjscomponents/microsoft_outlook/actions/list-labels/list-labels.mjscomponents/microsoft_outlook/actions/move-email-to-folder/move-email-to-folder.mjscomponents/microsoft_outlook/actions/remove-label-from-email/remove-label-from-email.mjscomponents/microsoft_outlook/actions/reply-to-email/reply-to-email.mjscomponents/microsoft_outlook/actions/send-email/send-email.mjscomponents/microsoft_outlook/actions/update-contact/update-contact.mjscomponents/microsoft_outlook/microsoft_outlook.app.mjscomponents/microsoft_outlook/package.jsoncomponents/microsoft_outlook/sources/new-attachment-received/new-attachment-received.mjscomponents/microsoft_outlook/sources/new-contact/new-contact.mjscomponents/microsoft_outlook/sources/new-email-in-shared-folder/new-email-in-shared-folder.mjscomponents/microsoft_outlook/sources/new-email/new-email.mjscomponents/neon_postgres/package.jsoncomponents/neon_postgres/sources/new-or-updated-row/new-or-updated-row.mjscomponents/nextcloud/actions/delete-share/delete-share.mjscomponents/nextcloud/package.jsoncomponents/nocodb/actions/add-record/add-record.mjscomponents/nocodb/actions/delete-record/delete-record.mjscomponents/nocodb/actions/get-record/get-record.mjscomponents/nocodb/actions/list-records-matching-criteria/list-records-matching-criteria.mjscomponents/nocodb/actions/update-record/update-record.mjscomponents/nocodb/nocodb.app.mjscomponents/nocodb/package.jsoncomponents/nocodb/sources/new-record-in-view/new-record-in-view.mjscomponents/nocodb/sources/new-record/new-record.mjscomponents/nocodb/sources/updated-record/updated-record.mjscomponents/ocrspace/actions/process-image/process-image.mjscomponents/ocrspace/actions/process-pdf/process-pdf.mjscomponents/ocrspace/ocrspace.app.mjscomponents/ocrspace/package.jsoncomponents/paigo/actions/create-dimension/create-dimension.mjscomponents/paigo/package.jsoncomponents/pennylane/actions/create-billing-subscription/create-billing-subscription.mjscomponents/pennylane/actions/create-customer-invoice/create-customer-invoice.mjscomponents/pennylane/actions/create-customer/create-customer.mjscomponents/pennylane/common/constants.mjscomponents/pennylane/package.jsoncomponents/postgresql/package.jsoncomponents/postgresql/sources/new-or-updated-row/new-or-updated-row.mjscomponents/printful/actions/create-order/create-order.mjscomponents/printful/package.jsoncomponents/quaderno/actions/create-contact/create-contact.mjscomponents/quaderno/package.jsoncomponents/quentn/actions/run-campaign-for-contact/run-campaign-for-contact.mjscomponents/quentn/package.jsoncomponents/reddit/actions/list-comments-in-a-post/list-comments-in-a-post.mjscomponents/reddit/actions/list-subreddits-by-query/list-subreddits-by-query.mjscomponents/reddit/actions/search-post/search-post.mjscomponents/reddit/actions/submit-a-comment/submit-a-comment.mjscomponents/reddit/actions/submit-a-post/submit-a-post.mjscomponents/reddit/package.jsoncomponents/reddit/reddit.app.mjscomponents/reddit/sources/new-comments-by-user/new-comments-by-user.mjscomponents/reddit/sources/new-comments-on-a-post/new-comments-on-a-post.mjscomponents/reddit/sources/new-hot-posts-on-a-subreddit/new-hot-posts-on-a-subreddit.mjscomponents/reddit/sources/new-links-by-user/new-links-by-user.mjscomponents/reddit/sources/new-links-on-a-subreddit/new-links-on-a-subreddit.mjscomponents/reddit/sources/new-private-message/new-private-message.mjscomponents/reddit/sources/new-saved-post-by-user/new-saved-post-by-user.mjscomponents/shopify/actions/update-inventory-level/update-inventory-level.mjscomponents/shopify/package.jsoncomponents/shopify_developer_app/README.mdcomponents/short_menu/actions/create-short-link/create-short-link.mjscomponents/short_menu/package.jsoncomponents/smartsheet/package.jsoncomponents/smartsheet/sources/new-row-updated/new-row-updated.mjscomponents/stiply/actions/send-sign-request/send-sign-request.mjscomponents/stiply/package.jsoncomponents/sumup/actions/get-merchant-profile/get-merchant-profile.mjscomponents/sumup/actions/list-transactions/list-transactions.mjscomponents/sumup/actions/retrieve-dba/retrieve-dba.mjscomponents/sumup/package.jsoncomponents/sumup/sources/new-transaction/new-transaction.mjscomponents/svix/actions/list-messages/list-messages.mjscomponents/svix/package.jsoncomponents/teamioo/actions/create-bookmark/create-bookmark.mjscomponents/teamioo/package.jsoncomponents/todoist/todoist.app.mjscomponents/wordpress_com/actions/upload-media/upload-media.mjscomponents/wordpress_com/common/utils.mjscomponents/wordpress_com/package.jsoncomponents/xero_accounting_api/actions/xero-accounting-create-or-update-contact/xero-accounting-create-or-update-contact.mjscomponents/xero_accounting_api/actions/xero-accounting-update-contact/xero-accounting-update-contact.mjscomponents/xero_accounting_api/package.jsonpackages/browsers/package.jsonpackages/connect-react/src/components/Label.tsxpackages/sdk/CONTRIBUTING.mdpackages/sdk/README.mdscripts/gitpod_api_wizard.shtypes/tsconfig.json
💤 Files with no reviewable changes (1)
- components/github/actions/common/utils.mjs
Collaborator
|
Hi @verhovsky, are you still working on this? |
Contributor
Author
|
No, it can be merged. |
Collaborator
@verhovsky Awesome! Can you fix the merge conflicts? Also, it's failing some checks. |
michelle0927
approved these changes
Mar 18, 2026
github-project-automation
Bot
moved this from Doing
to Done
in Component (Source and Action) Backlog
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit
Bug Fixes
Chores
Documentation