Repair basic RB registry integration #326
Merged
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
come on it's the year 2022
the original regex was too loose, it picked up variable specs of the form ${name}
and then tried to evaluate "name".
Replaced with an exact match for ${generateUuid()} since that's all we support anyway.
to avoid npm woes from overly strict peerdep on editor
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.
The main issue was a broken regex in the instantiateUuids function imported from the template variable plugin
the original regex was too loose, it picked up variable specs of the form ${name} and then tried to evaluate "name".
Replaced with an exact match for ${generateUuid()} since that's all we support anyway.