-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix(parser): allow to visit typeParameters in OptionalCallExpression #1377
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
foo?.bar<A>(); | ||
foo?.bar<number>(); | ||
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -51,8 +51,8 @@ interface ASTAndProgram { | |||||
|
||||||
/** | ||||||
* @param code The code of the file being linted | ||||||
* @param options The config object | ||||||
* @param shouldProvideParserServices True iff the program should be attempted to be calculated from provided tsconfig files | ||||||
* @param shouldProvideParserServices True if the program should be attempted to be calculated from provided tsconfig files | ||||||
* @param shouldCreateDefaultProgram True if the program should be created from compiler host | ||||||
* @returns Returns a source file and program corresponding to the linted code | ||||||
*/ | ||||||
function getProgramAndAST( | ||||||
|
@@ -366,7 +366,7 @@ function parseAndGenerateServices<T extends TSESTreeOptions = TSESTreeOptions>( | |||||
)!; | ||||||
|
||||||
/** | ||||||
* Determine whether or not two-way maps of converted AST nodes should be preserved | ||||||
* Determine whatever or not two-way maps of converted AST nodes should be preserved | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. wasn't this correct? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @BO41 hmm, you might be right, "whatever or not" seems weird
i think it will be safer to change it to
Suggested change
what do you think? i'm not that good at grammar There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. just the "if" sounds good 👍 |
||||||
* during the conversion process | ||||||
*/ | ||||||
const shouldPreserveNodeMaps = | ||||||
|
Uh oh!
There was an error while loading. Please reload this page.