improved macro node #162
Merged
improved macro node #162
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
This PR enhances most stdlib macro nodes with the ability to expose dynamic values from within certain fields.
For example, before this change, if one wanted to make an HTTP request to a partially-dynamic URL (i.e
https://exame.com/?name={{name}}- the URL field had to be set as "dynamic", and a new expression node was needed to build the URL.Now, you can just expose the dynamic variable from within the field itself:
Screen.Recording.2024-10-04.at.22.14.41.mov
This PR also includes utilities do create such "improved" macro nodes faster, and many other cleanups related to this effort