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
[labs/analyzer] Don't extract JSDoc types in TS. Port type tests to JS. #3658
Merged
Conversation
This file contains 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
…if applicable. (...) When TypeScript is checking `.ts` files, JSDoc comments that indicate types have no effect despite being parsed and reachable through the AST. When checking `.js` files, JSDoc comments are automatically considered by `tsc` and don't need to be separately taken into account.
🦋 Changeset detectedLatest commit: 70e8068 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
|
These tests were checking if types defined by JSDoc comments in `.ts` files were being output by the analyzer. However, TS does not consider JSDoc comments to have any effect in `.ts` files, even though they're parsed and reachable in the AST.
bicknellr
force-pushed
the
analyzer-jsdoc-types-tests
branch
from
February 8, 2023 23:09
a76ca1e
to
c98dab8
Compare
bicknellr
changed the title
[labs/analyzer] Port type tests to JS.
[labs/analyzer] Don't extract JSDoc types in TS. Port type tests to JS.
Feb 8, 2023
bicknellr
commented
Feb 8, 2023
justinfagnani
approved these changes
Feb 8, 2023
kevinpschaaf
approved these changes
Feb 9, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
TS doesn't consider types provided in JSDoc comments as having any effect in
.ts
files, even though they're still accessible in the AST. This PR updates the analyzer to match this behavior and also copies/ports the type tests to JS to confirm that JSDoc comments still affect the analysis of.js
files.This PR is easier to read with leading whitespace removed.