-
Notifications
You must be signed in to change notification settings - Fork 130
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
Attempt to fix #154 #179
Attempt to fix #154 #179
Conversation
Hi @chadhietala, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution! TTYL, MSBOT; |
Hey @chadhietala, as a heads up, mentioning the issue you're fixing in the PR body actually links to it, and the PR title itself should typically be more descriptive so readers don't have to navigate to the original issue for full context. @anubmat can you take a look at this? |
@chadhietala, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR. |
Not sure how important the CLA is now that I will be working at a MS subsidiary... 😄 |
"editor.insertSpaces": true, | ||
"files.trimTrailingWhitespace": false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can remove this. I think I'm using this extension that adds a new line and tests care about whitespace.
@chadhietala, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR. |
f5dbf79
to
c4930a9
Compare
Attempt to fix microsoft#154
c4930a9
to
71f3172
Compare
@@ -154,15 +154,15 @@ repository: | |||
|
|||
method-declaration: | |||
name: meta.method.declaration.ts | |||
begin: '\b(?:(abstract)\s+)?\b(?:(public|private|protected)\s+)?\b(?:(async)\s+)?(?:(get|set)\s+)?(?:(new)|(?:\b(constructor)\b)|(?:([a-zA-Z_$][\.\w$]*)\s*(\??)))?\s*(?=\(|\<)' | |||
begin: '\b(?:(abstract)\s+)?\b(?:(public|private|protected)\s+)?\b(?:(async)\s+)?(?:(get|set)\s+)?(?:(new)|(?:\b(constructor)\b)|(?:(\[*)(`|'|"*)(.*)(`|'|"*)(\]*)\s*(\??)))?\s*(?=\(|\<)' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This still doesn't look correct. For example, the .*
would eat everything including the closing quote and bracket (the test case needs to be updated for it). Also, do you need to consider if the two quotes are matching? For example, ["test']
and ['test"]
shouldn't be treated the same way as the ["test"]
The original issue should be fixed now by #257 |
I actually have no idea if this is correct or not but thought I would put it up to get some feedback.
_Edit by @DanielRosenwasser:_ Fixes #154.