-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Replace errorType return with Debug fail in checkExpressionWorker #54117
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
Open
weswigham
wants to merge
4
commits into
microsoft:main
Choose a base branch
from
weswigham:cew-debug-fail
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
d7dabe8
Replace errorType return with Debug fail in checkExpressionWorker
weswigham d36de35
Add `ImportKeyword` to checkExpressionWorker even though its not flag…
weswigham fc0ae95
Add a couple more non-explicit entries to checkExpressionWorker
weswigham 7dfe497
Make invalid syntax uses of ImportKeyword expressions the errorType
weswigham File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@rbuckton should this be an expression? It's not flagged by
isExpressionNode
, but is definitely assigned to expression-expecting node positions.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.
We have two different ways to test for expressions, so we may need to verify both are correct:
isExpression
in utilitiesPublic.ts — Tests whether aNode
is a subtype ofExpression
. Doesn't care about context (i.e., no.parent
access). Designed for use with transformers (where.parent
may not be set).isExpressionNode
in _utilities.ts — Tests whether aNode
is used in an expression position. Highly contextual (performs.parent
lookups). Used by the checker, though I'd love to find a way to retire it at some point.