Skip to content

Conversation

@MarlonRodriguez
Copy link

Fixed a bug with empty double quoted strings ("") which would bleed ignoring the closing quote.
Fixed a bug where double quoted strings ending in "`" would incorrectly show as closed strings.

Fixed a bug with empty double quoted strings ("") which would bleed ignoring the closing quote.
Fixed a bug where double quoted strings ending in "`" would incorrectly show as closed strings.
@MarlonRodriguez
Copy link
Author

Please make this change to fix the bug mentioned in the second commits comment.

Used "Get-Verb" to gather all the approved verbs and removed any not "approved"
Removed last space from the verbs variable.
Updated Keywords variable
@MarlonRodriguez
Copy link
Author

Latest commits will update verbs and keywords.

@MarlonRodriguez MarlonRodriguez changed the title Fix for double quote strings in powershell brush Fix for double/single quote strings in powershell brush and updated verbs and keywords Feb 9, 2016
@alexgorbatchev alexgorbatchev self-assigned this Feb 9, 2016
@alexgorbatchev
Copy link
Member

Thank you! I'll merge this shortly.

@MarlonRodriguez
Copy link
Author

np. Seems like it might be a bit obsolete now that you are gearing up v4 dev merge? I took a quick look and your use of XRegEx will mean a redo of this repo as well.

@FISHMANPET
Copy link

Is there a reason this never got merged? I was about to make these changes myself and make a PR but I see the work has already been done.

@MarlonRodriguez
Copy link
Author

I think it was the fact that the new version treats it differently with different syntax and this might be different. Since I didn't have the new dev branch of v4 I didn't dig in it.

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.

3 participants