-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Refactor: Print ChainExpression directly #10244
Copy link
Copy link
Closed
Labels
help wantedWe're a small group who can't get to every issue promptly. We’d appreciate help fixing this issue!We're a small group who can't get to every issue promptly. We’d appreciate help fixing this issue!lang:javascriptIssues affecting JSIssues affecting JSlocked-due-to-inactivityPlease open a new issue and fill out the template instead of commenting.Please open a new issue and fill out the template instead of commenting.type:refactorIssues about tackling technical debtIssues about tackling technical debt
Description
Metadata
Metadata
Assignees
Labels
help wantedWe're a small group who can't get to every issue promptly. We’d appreciate help fixing this issue!We're a small group who can't get to every issue promptly. We’d appreciate help fixing this issue!lang:javascriptIssues affecting JSIssues affecting JSlocked-due-to-inactivityPlease open a new issue and fill out the template instead of commenting.Please open a new issue and fill out the template instead of commenting.type:refactorIssues about tackling technical debtIssues about tackling technical debt
Currently, we are transforming
ChainElements toOptionalCallExpressionandOptionalMemberExpression.It's supposed to be a temporary workaround for
espreeandmeriyahparser, nowtypescriptparser use this AST type too, it's a standardestreeAST, we should support print it directly.This refactor may need a big change in
CallExpressionMemberExpressionrelated logic part.