Skip to content

fix: rename user-facing 'API Nodes' to 'Partner Nodes' #13005

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.

Sign up for GitHub

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

Open
marawan206 wants to merge 1 commit into
base: main
Choose a base branch
from
+6 −6
Open

fix: rename user-facing 'API Nodes' to 'Partner Nodes' #13005

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions src/locales/en/main.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1506,7 +1506,7 @@
"Light": "Light",
"User": "User",
"Credits": "Credits",
"API Nodes": "API Nodes",
"API Nodes": "Partner Nodes",
"Notification Preferences": "Notification Preferences",
"3DViewer": "3DViewer",
"Canvas Navigation": "Canvas Navigation",
Expand Down Expand Up @@ -1966,11 +1966,11 @@
"accessRestrictedMessage": "Your account is not authorized for this feature."
},
"apiNodesSignInDialog": {
"title": "Sign In Required to Use API Nodes",
"message": "This workflow contains API Nodes, which require you to be signed in to your account in order to run."
"title": "Sign In Required to Use Partner Nodes",
"message": "This workflow contains Partner Nodes, which require you to be signed in to your account in order to run."

@coderabbitai coderabbitai Bot Jun 19, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Line 1970 exceeds the 80-character width limit.

The apiNodesSignInDialog.message string is approximately 145 characters, which violates the coding guideline of 80-character width. Consider splitting the message value into multiple lines or abbreviating the text to fit within the width constraint.

💡 Suggested fix to comply with 80-character width

One option is to break the message into multiple logical parts (note: JSON structure may require careful handling):

  "apiNodesSignInDialog": {
    "title": "Sign In Required to Use Partner Nodes",
-   "message": "This workflow contains Partner Nodes, which require you to be signed in to your account in order to run."
+   "message": "This workflow contains Partner Nodes, which require you to be signed in to your account in order to run"
  },

Alternatively, if the message content can be shortened:

-   "message": "This workflow contains Partner Nodes, which require you to be signed in to your account in order to run."
+   "message": "This workflow uses Partner Nodes. Sign in to your account to run it."
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"message": "This workflow contains Partner Nodes, which require you to be signed in to your account in order to run."
"message": "This workflow uses Partner Nodes. Sign in to your account to run it."
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/locales/en/main.json` at line 1970, The message value for
apiNodesSignInDialog.message in the JSON file exceeds the 80-character width
limit at approximately 145 characters. To fix this, split the message into
multiple logical parts by breaking it at natural language boundaries (such as
after "Partner Nodes," or "to your account,") and recombine them using proper
JSON string concatenation or restructure the message to be more concise while
preserving its meaning. Ensure the final result complies with the 80-character
line width constraint.

Source: Coding guidelines

},
"apiNodesCostBreakdown": {
"title": "API Node(s)",
"title": "Partner Node(s)",
"costPerRun": "Cost per run",
"totalCost": "Total Cost"
},
Expand Down Expand Up @@ -2229,7 +2229,7 @@
"apiKey": {
"title": "API Key",
"label": "API Key",
"description": "Use your Comfy API key to enable API Nodes",
"description": "Use your Comfy API key to enable Partner Nodes",
"placeholder": "Enter your API Key",
"error": "Invalid API Key",
"storageFailed": "Failed to store API Key",
Expand Down Expand Up @@ -2340,7 +2340,7 @@
"cancel": "Cancel"
},
"loginButton": {
"tooltipHelp": "Login to be able to use \"API Nodes\"",
"tooltipHelp": "Login to be able to use \"Partner Nodes\"",
"tooltipLearnMore": "Learn more..."
}
},
Expand Down
Loading