Repository navigation
Load the chosen template's merge fields in Render Template - #10
Merged
Merged
Conversation
Merged
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
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.
Load the chosen template's merge fields in Render Template
Render Template makes people type each placeholder name by hand, and a wrong or missing name renders as a raw placeholder or fails the render.
Merge Fields Source gets a From Template option that lists the chosen template's merge fields, one input each. A field left empty, or added to the template later, goes out with the template's own value, read once per run from
GET /templates/{id}. The inputs are text, because n8n's type check refuses a sheet's "5" in a number field, so the node gives each value the type of the template's own value.Node version 2 makes From Template the default. n8n leaves defaults out of saved workflows, so changing version 1's default would switch every saved step. Saved steps stay on version 1, default to Fields and send the same request as before. Version 1 gets the option too, so saved steps can switch without a rebuild (MAINTAINING.md now allows this). There is no flag: the node version is the gate.
Verify:
node scripts/review-check.mjs40/40;npm test98 pass, includingtest/template-fields.mjs.Risk: none for saved steps. Revert to roll back.