fix(typescript-estree): handle BigInt
with _
numeric separator
#2067
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.
Fix
BigInt
withnumberic separator
parsing.The estree spec only said
n
should not include inbigint
,so I guess._
should perserveUpdate: The spec says
bigint property is the string representation of the BigInt value
, and we are usingString(BigInt('123'))
for1_2_3n
, it doesn't includes_
, so it should not include_
.