Skip to content
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

Properly escape property value to handle non string types #311

Merged
merged 3 commits into from
Feb 8, 2018

Conversation

stephenmichaelf
Copy link
Member

No description provided.

@ericsciple
Copy link
Contributor

ericsciple commented Feb 8, 2018 via email

@stephenmichaelf
Copy link
Member Author

@ericsciple Comment and tests added.

@@ -32,7 +32,9 @@ export class TaskCommand {
if (this.properties.hasOwnProperty(key)) {
var val = this.properties[key];
if (val) {
cmdStr += key + '=' + escape(val) + ';';
// safely append the message - avoid blowing up when attempting to
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

message => val

@ericsciple
Copy link
Contributor

looks good

@stephenmichaelf stephenmichaelf changed the title Fix. Properly escape property value to handle non string types Feb 8, 2018
@stephenmichaelf stephenmichaelf merged commit b7b47e4 into master Feb 8, 2018
@bryanmacfarlane
Copy link
Contributor

published as 2.2.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants