GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||||||||
GeezerVison is showing github.com — Fixed multiple prologue directives with parameter properties by JoshuaKGoldberg · Pull Request #48687 · microsoft/TypeScript Conversation
|
| break; | ||
| } | ||
| if (!isPrologueDirective(statement) && nodeImmediatelyReferencesSuperOrThis(statement)) { | ||
| if (nodeImmediatelyReferencesSuperOrThis(statement)) { |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
This change isn't necessary for the PR; I just had only noticed the check is unnecessary after #29374 was merged 😄
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| const indexAfterLastPrologueStatement = factory.copyPrologue(body.statements, statements, /*ensureUseStrict*/ false, visitor); | ||
| const superStatementIndex = findSuperStatementIndex(body.statements, indexAfterLastPrologueStatement); | ||
| const prologueStatementCount = factory.copyPrologue(body.statements, statements, /*ensureUseStrict*/ false, visitor); | ||
| const superStatementIndex = findSuperStatementIndex(body.statements, prologueStatementCount); |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I'm nitpicking the variable name here. Both variable names are correct; prologueStatementCount just makes more sense to me -- especially in the context of the new array spread below.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks for fixing this! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
TypeScript Bot (@typescript-bot) cherry-pick this to release-4.6 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Heya Jake Bailey (@jakebailey), I've started to run the task to cherry-pick this into |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Hey Jake Bailey (@jakebailey), I couldn't open a PR with the cherry-pick. (You can check the log here). You may need to squash and pick this PR into release-4.6 manually. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sent #48782 manually. This PR is needed for the other PRs thanks to this PR affecting the base |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…#48782) Co-authored-by: Josh Goldberg <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
No-op string in constructor is repeated and reordered when constructor assignment is used
There was an error while loading. Please reload this page.