Properly escape property value to handle non string types #311
Conversation
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
Contributor
|
Looks good can you add the same comment from below in the file and an L0
|
Member
Author
|
@ericsciple Comment and tests added. |
ericsciple
reviewed
Feb 8, 2018
node/taskcommand.ts
Outdated
| var val = this.properties[key]; | ||
| if (val) { | ||
| cmdStr += key + '=' + escape(val) + ';'; | ||
| // safely append the message - avoid blowing up when attempting to |
Contributor
|
looks good |
stephenmichaelf
changed the title
Contributor
|
published as 2.2.1 |
fullstackinfo
pushed a commit
to fullstackinfo/azure-pipelines-task-lib
that referenced
this pull request
Aug 17, 2024
Properly escape property value to handle non string types
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.
No description provided.