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
[pipeline operator] support await #6889
Comments
Will not continue to support |
Sorry I don't understand your point @lilijialiang. This is only an addition to the existing support in Babel. |
Does the spec actually support this? The example in the README only shows x |> await f which is an equivalent of await f And in the current grammar defined in the spec draft, there is no option for a RHS without a LogicalORExpression expansion. EDIT: I just saw the discussion in tc39/proposal-pipeline-operator#66 and corresponding PR tc39/proposal-pipeline-operator#71 which explains that this used to be supported but no longer is. |
This is not currently specced yet but will be supported in the parser in #7458 and eventually added as an option in the pipeline plugin. |
Should this be closed? |
@thiagoarrais I'll be implementing this as part of the F# parsing. It's not strictly necessary to track but isn't technically "resolved". Up to the maintainers what they want to do here. |
Sorry for the noise. I interpreted that this was already implemented in F#. |
I added this to https://github.com/babel/babel/projects/9#card-17016058 so we don't forget to close it when it is fixed |
Supported by #9984 |
Choose one: is this a bug report or feature request?
Input Code
which is the equivalent of
Expected Behavior
Current Behavior
Possible Solution
Context
Your Environment
As described in the spec here.
The text was updated successfully, but these errors were encountered: