Add Variable Name Validation and Wrapper Control #6117
Merged
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 adds an option to disable the automatic wrapper generation of C# and JavaScript functions for workflow variables.
Changes:
C# Syntax:
When opting out,
Variables.MyVariable
will no longer be available. Variables can only be accessed using:Variables.Get("MyVariable")
Variables.Get<T>("MyVariable")
Configuration:
To disable wrappers in C#, use the following configuration:
JavaScript Syntax:
When opting out,
variables.MyVariable
andgetMyVariable()
will no longer be available. Variables can only be accessed using:getVariable("MyVariable")
Configuration:
To disable wrappers in JavaScript, use the following configuration:
Use Case:
This feature is helpful for applications requiring the use of variable names that are invalid in JavaScript or C#.
This change is