-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Fix issue #5444 #5566
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
Fix issue #5444 #5566
Conversation
reportImplementationExpectedError: The next node in the tree is not necessarily consecutive. This happens due to syntax errors, e.g. class C { foo(), foo(); }
Hi @jeffreymorlan, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution! TTYL, MSBOT; |
Can you please add unit tests. |
To be clear, @mhegazy does't mean a unit test, he means an end-to-end test. Check out Adding a Test in our CONTRIBUTING.md. |
@@ -11205,7 +11205,7 @@ namespace ts { | |||
seen = c === node; | |||
} | |||
}); | |||
if (subsequentNode) { | |||
if (subsequentNode && subsequentNode.pos === node.end) { |
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.
Can you add a comment that you need this test because garbage declarations may be introduced between overloads and cause issues according to our expectations
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.
Done
👍 @vladima could you take a look? |
👍 after @DanielRosenwasser note about the comment is addressed |
reportImplementationExpectedError: The next node in the tree is not
necessarily consecutive. This happens due to syntax errors, e.g.
Edit by @DanielRosenwasser: Fixes #5444