-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
feat(core): Add batching and other options to declarative nodes #8885
Conversation
Excited to see this! A few questions if you don't mind:
|
@pemontto to your questions
Both things could obviously be added in the future if there is a strong demand |
…ing-to-declarative-style
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.
LGTM, I had to add // eslint-disable-next-line complexity
for runNode
, but I guess this is expected here
1 flaky test on run #5332 ↗︎
Details:
cypress/e2e/5-ndv.cy.ts • 1 flaky test
Review all test suite changes for PR #8885 ↗︎ |
✅ All Cypress E2E specs passed |
Co-authored-by: Michael Kret <[email protected]>
Got released with |
@janober good evening, is this adjustment now available for the community edition? |
It is available in all versions. The problem is just hat the OpenAI node got changed for different reasons and is now not declarative anymore for that reason did it not work with that node anymore. Will however work with v1 of the node. So if you change it to that one it should work. Let me know if you do not know how. |
Thank you for the quick return, I don't know how to use the node v1. Could you teach me? Thanks |
@janober is there any desire or plan to make openai declative again? about changing the node version, I used GPT and it told me that I need to change the configuration files on the server, is that it? |
@juniorgregio Sorry, did miss your answer. To get version 1 of the node you can simply copy the following and paste it into n8n:
Sadly, it is not currently planned to make it declarative again, as it would bring other disadvantages that are very specific to the node and its usage (details would be too complex to explain right now). Sorry. |
Thanks for the feedback @janober , it's helped a lot but I still have questions about where exactly to paste it on the N8N? |
@juniorgregio straight onto the workflow canvas! 😉 |
Summary
Adds support for
to all declarative nodes.
FYI:
displayOptions
. So do different Resource -> Operation combinations often share parameters or have totally separate ones.As there is no easy way (for sure possible, but none that would not increase the scope of this originally simple and fast extension) of ensuring that the options get reliably displayed properly for all combinations, did we decide to move it into Node-Settings.
Related tickets and issues
https://community.n8n.io/t/langchain-and-openai-nodes-should-be-able-to-parallel-requests-like-http-node/40383/2
Review / Merge checklist
(no-changelog)
otherwise. (conventions)