-
Notifications
You must be signed in to change notification settings - Fork 1k
[labs/analyzer] Collect up diagnostics rather than throwing on unexpected (legal) conditions #3866
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
Conversation
…`ts.DiagnosticCategory`.
I thought it might be useful to collect diagnostics for each module individually and also have a single list with all diagnostics in a program, but there's nothing that needs this right now.
This mostly reverts commit 24ba127, but leaves the part that ignores function overloads.
…ith unsupported name types.
…h non-identifiers.
…nilla JS classes.
This reverts commit 1a98ee7.
🦋 Changeset detectedLatest commit: de6f820 The changes in this PR will be included in the next version bump. This PR includes changesets to release 7 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
📊 Tachometer Benchmark ResultsSummarynop-update
render
update
update-reflect
Resultslit-element-list
render
update
update-reflect
lit-html-kitchen-sink
render
update
nop-update
lit-html-repeat
render
update
lit-html-template-heavy
render
update
reactive-element-list
render
update
update-reflect
|
Also start with one diagnostic category that's informative ("we don't know how to handle this yet"), and put the rest into the wastebasket taxon
justinfagnani
left a comment
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.
Nice! A few comments, but none a big deal.
No description provided.