-
Notifications
You must be signed in to change notification settings - Fork 7.1k
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(HTTP Request Node): Handle special characters in pagination expressions + improve hint text #8576
fix(HTTP Request Node): Handle special characters in pagination expressions + improve hint text #8576
Conversation
…node-name-makes-pagination
…http-request-node-apostrophe-in-node-name-makes-pagination
throw new NodeOperationError(node, `'${paginateRequestData.url}' is not a valid URL.`, { | ||
itemIndex, | ||
runIndex, | ||
type: 'invalid_url', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would avoid extending NodeApiError interface for this special case, as this error would be replaced in Http node anyway we could send some technical message for identification
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer using a type
to check on instead of using the message. We also use this pattern for other errors (like ExpressionError)
…node-name-makes-pagination
1 flaky test on run #4083 ↗︎
Details:
cypress/e2e/5-ndv.cy.ts • 1 flaky test
Review all test suite changes for PR #8576 ↗︎ |
✅ All Cypress E2E specs passed |
Got released with |
…ssions + improve hint text (#8576) Co-authored-by: Michael Kret <michael.k@radency.com>
Summary
Related tickets and issues
https://linear.app/n8n/issue/NODE-1097/http-request-node-apostrophe-in-node-name-makes-pagination-expressions
Review / Merge checklist
(no-changelog)
otherwise. (conventions)