Skip to content

Conversation

Joffcom
Copy link
Member

@Joffcom Joffcom commented Sep 1, 2025

No description provided.

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

3 issues found across 85 files

React with 👍 or 👎 to teach cubic. You can also tag @cubic-dev-ai to give feedback, ask questions, or re-run the review.

@@ -33,6 +33,22 @@
"kind": {
"type": "string"
},
"localizations": {
Copy link
Contributor

Choose a reason for hiding this comment

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

localizations defines only the 'en' key, leaving other locale keys unconstrained; model all locales with patternProperties or additionalProperties so each locale maps to { title, description }.

(Based on your team's feedback about keeping review comments concise, this focuses on the specific schema shape change.)

Prompt for AI agents
Address the following comment on packages/nodes-base/nodes/Google/YouTube/__schema__/v1.0.0/video/get.json at line 36:

<comment>localizations defines only the &#39;en&#39; key, leaving other locale keys unconstrained; model all locales with patternProperties or additionalProperties so each locale maps to { title, description }.

(Based on your team&#39;s feedback about keeping review comments concise, this focuses on the specific schema shape change.)</comment>

<file context>
@@ -33,6 +33,22 @@
         &quot;kind&quot;: {
             &quot;type&quot;: &quot;string&quot;
         },
+        &quot;localizations&quot;: {
+            &quot;type&quot;: &quot;object&quot;,
+            &quot;properties&quot;: {
</file context>

"type": "null"
},
"SystemModstamp": {
"error": {
Copy link
Contributor

Choose a reason for hiding this comment

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

Replacing the account GET schema with an error string field is inconsistent with other GET schemas and likely incorrect; GET schemas enumerate object fields, not an error-only shape.

(Based on your team's feedback about not assuming prior response shape, I verified by comparing other Salesforce get.json schemas and searching the repo for error fields in get.json.)

Prompt for AI agents
Address the following comment on packages/nodes-base/nodes/Salesforce/__schema__/v1.0.0/account/get.json at line 4:

<comment>Replacing the account GET schema with an error string field is inconsistent with other GET schemas and likely incorrect; GET schemas enumerate object fields, not an error-only shape.

(Based on your team&#39;s feedback about not assuming prior response shape, I verified by comparing other Salesforce get.json schemas and searching the repo for error fields in get.json.)</comment>

<file context>
@@ -1,56 +1,9 @@
-            &quot;type&quot;: &quot;null&quot;
-        },
-        &quot;SystemModstamp&quot;: {
+        &quot;error&quot;: {
             &quot;type&quot;: &quot;string&quot;
         }
</file context>

"id": {
"type": "string"
},
"preferredLanguage": {
"type": "null"
Copy link
Contributor

Choose a reason for hiding this comment

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

preferredLanguage is constrained to null-only; it should allow string (and optionally null) to match the expected user resource contract and avoid rejecting valid values.

Prompt for AI agents
Address the following comment on packages/nodes-base/nodes/Microsoft/Entra/__schema__/v1.0.0/user/create.json at line 23:

<comment>preferredLanguage is constrained to null-only; it should allow string (and optionally null) to match the expected user resource contract and avoid rejecting valid values.</comment>

<file context>
@@ -16,15 +16,15 @@
             &quot;type&quot;: &quot;string&quot;
         },
+        &quot;preferredLanguage&quot;: {
+            &quot;type&quot;: &quot;null&quot;
+        },
         &quot;userPrincipalName&quot;: {
</file context>

Copy link

codecov bot commented Sep 1, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@n8n-assistant n8n-assistant bot added n8n team Authored by the n8n team node/improvement New feature or request labels Sep 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
n8n team Authored by the n8n team node/improvement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant