-
Notifications
You must be signed in to change notification settings - Fork 0
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(global-context): Adding a "global context" instead of interpolate #378
Conversation
- flow element placeholder path variables are now replaced on every update or init with the corresponding explicit values
🦋 Changeset detectedLatest commit: d008d8d The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
let newValue = value; | ||
let m: RegExpExecArray; | ||
do { | ||
m = blockRegEx.exec(value); |
Check failure
Code scanning / CodeQL
Polynomial regular expression used on uncontrolled data High
regular expression
library input
This
regular expression
library input
This
regular expression
library input
This
regular expression
library input
- test for the context manager and its purpose / usage - properties object with the placeholder property-object in flow elements to be able to replace with new values at update
Quality Gate passedIssues Measures |
If the properties of the flow change, some of these are not adopted by the elements, which is why they should first be set in the elements by means of a “global context / a context manager” in the flow application at every update.