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.
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
typecheck updates & fixes in src/language-js #8759
typecheck updates & fixes in src/language-js #8759
Changes from 79 commits
d2e5a9e
4bde973
1959b8e
cf8fd21
6fde6d1
aed44b2
8b420bf
f510935
865f365
9abf8a1
a728b7e
d307f74
eefa0de
a5d5ee7
171343a
82e9caa
3862b26
ba4148b
46e7b6d
33bcf98
9a0c756
e2cc79b
3ae14db
7a44932
ea6c5ae
965b614
571b60a
f4a7c06
c3701ed
5e69ad7
51b3382
3babd0e
b6decaf
0a7e566
95d7ff6
e293270
098ef04
0ffb531
be02bca
52add90
1cefd9c
d865280
895ce87
9bf9af3
5e7c3ce
11b72c4
002d065
a620d67
ebd102f
f8483ad
cd6ae5a
d41c75a
a66e43a
736dc79
d5da9b6
5cc4cdc
3cb1743
21f9358
8eb54e4
f95fb88
ddc404a
e0ef929
ea68916
767a909
954fd9b
ce5c4cb
a440d85
8ac1080
062f8b7
a4c02af
d988fcf
ea7d224
983a099
435b9c3
cd52842
5414a62
8a6e970
c6662a6
83bd956
5346498
1979c45
29b43a7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Do we have to do this ? sting.type can't be
group
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.
I added the
typeof part !== "string"
condition to resolve a JSDoc type error.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.
I know, I mean, this can't do in other way ?
I know nothing about JSDoc
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.
I would have to investigate. I guess we could use
@ts-ignore
comment for now.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.
Will
part && part.type === "group"
work ? It make sense to me .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.
I think not because IMHO
part
could be a string.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.
As I said, even if it's string, there is nothing wrong checking
String.type
...I'm going to give up, this JSDoc thing is driving me crazy. 😄
If other contributors think it's okay, I'm okay with it too.
Thank you for explaining this.
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.
The whole JSDoc thing can be a bit crazy. There used to be very few users, now seem to be more and more. I would be happy to post some resources if you like, maybe someday later. We can see it is basically shoehorning quite a bit of TypeScript capabilities into documentation comments. I do really like that it cleanly separates type checking away from executable JavaScript code, can sure be a bit messy though :)
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.
No... thanks , I don't want, I don't use typescript either.
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.
This will work even with TypeScript 4.x:
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.
Thanks @ExE-Boss. I would actually favor keeping this workaround as-is, errors can remind us to remove it with the TypeScript 4 update. Nice idea, though.
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 should be able to remove this entire workaround if typescript-eslint/typescript-eslint#2405 is merged and released. I hope this will be possible.