Skip to content
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

fix(typescript-estree): correct parenthesized optional chain AST #1141

Merged
merged 4 commits into from Oct 25, 2019

Conversation

bradzacher
Copy link
Member

@bradzacher bradzacher commented Oct 25, 2019

Fixes #1139

Also fixes the package not working in the browser (ts.sys === undefined in the browser).

The snapshots are getting pretty ugly now.
I think we need a new system for them (#1142).

I tested this via a local build of ASTExplorer.
Sidebar - we should really maintain our own version of it (#1143).

@bradzacher bradzacher added the bug Something isn't working label Oct 25, 2019
@typescript-eslint
Copy link
Contributor

Thanks for the PR, @bradzacher!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!


🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day.

@codecov
Copy link

codecov bot commented Oct 25, 2019

Codecov Report

Merging #1141 into master will decrease coverage by 0.03%.
The diff coverage is 89.47%.

@@            Coverage Diff             @@
##           master    #1141      +/-   ##
==========================================
- Coverage   94.07%   94.03%   -0.04%     
==========================================
  Files         120      120              
  Lines        5214     5217       +3     
  Branches     1443     1445       +2     
==========================================
+ Hits         4905     4906       +1     
  Misses        177      177              
- Partials      132      134       +2
Impacted Files Coverage Δ
packages/typescript-estree/src/convert.ts 98.99% <100%> (ø) ⬆️
...ges/typescript-estree/src/create-program/shared.ts 75% <50%> (-5%) ⬇️
packages/typescript-estree/src/parser.ts 94.82% <87.5%> (-0.79%) ⬇️

JamesHenry
JamesHenry previously approved these changes Oct 25, 2019
@thorn0
Copy link
Contributor

thorn0 commented Oct 25, 2019

Please update also SUPPORTED_TYPESCRIPT_VERSIONS. It doesn't include 3.7.1-rc.

@thorn0
Copy link
Contributor

thorn0 commented Oct 25, 2019

warnAboutTSVersion also fails in the browser because of process.stdout.isTTY.

];
extra.log(versionWarning.join('\n\n'));
if (!isRunningSupportedTypeScriptVersion && !warnedAboutTSVersion) {
const isTTY = typeof process === undefined ? false : process.stdout.isTTY;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In Prettier's build configuration, we have process, but not process.stdout. 🤷‍♂️

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

darn...

probably just better to do what parser does, and clear the logger function:

const warnOnUnsupportedTypeScriptVersion = validateBoolean(
options.warnOnUnsupportedTypeScriptVersion,
true,
);
if (!warnOnUnsupportedTypeScriptVersion) {
parserOptions.loggerFn = false;
}

(note that this logger function isn't used anywhere else, it's only used to log the warning)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Optional chaining: (a?.b).c is parsed as a?.b.c
3 participants