proposal-pipeline-operator icon indicating copy to clipboard operation
proposal-pipeline-operator copied to clipboard

A proposal for adding a useful pipe operator to JavaScript.

Results 40 proposal-pipeline-operator issues
Sort by recently updated
recently updated
newest added

I wanted to propose adding an optional placeholder name to the syntax and ask you what do you think about it? Example: ```ts const fileName = "file.txt"; fileName |> addServerPath(%)...

follow-on proposal

This issue is for **bikeshedding the spelling of the topic reference’s token** in [Hack pipes][], branching off from https://github.com/tc39/proposal-pipeline-operator/issues/75#issuecomment-362850526. The **[table has its own editable page on the wiki](https://github.com/tc39/proposal-pipeline-operator/wiki/Bikeshedding-the-Hack-topic-token/)**. Please...

bikeshed

I was excited today to see the Function.pipe/flow proposal. I think the direction of standardizing ECMAScript APIs to solve the well-known problems of callback complexity is something that should be...

question
documentation

Spinning this out of https://github.com/tc39/proposal-pipeline-operator/issues/202#issuecomment-919374937. Lots of people have expressed concerns that Hack pipes would silo the community of JavaScript [tacit-programming][tacit programming] (aka point-free style). These fears are understandable. And...

documentation

Given that the hack pipeline doesn't really adequately meet the goals for folks trying to mimic method chains (aka "fluent" interfaces), it seems like the [section on method chaining](https://github.com/tc39/proposal-pipeline-operator/tree/265f2f0e8158d5770bfe9e076084cd3a4e82fd5a#method-chaining-is-limited) might...

question
documentation

* [F#-style pipes][], [partial function application (PFA)][PFA], unary function composition ([Function.pipe / flow][]), and [currying][] all are techniques of a paradigm called **[tacit / point-free programming][tacit]**. * Tacit / point-free...

documentation

As per 2022-03-29 plenary. See https://github.com/tc39/proposal-pipeline-operator/issues/91#issuecomment-1082239465, https://github.com/tc39/proposal-pipeline-operator/issues/91#issuecomment-1085006912, https://github.com/tc39/proposal-pipeline-operator/issues/91#issuecomment-1085006912. Also adds a paragraph addressing https://github.com/tc39/proposal-decorators/issues/430#issuecomment-1084968459 and https://github.com/tc39/proposal-pipeline-operator/issues/91#issuecomment-1084946624.

To read a detailed history of this proposal, please see [HISTORY.md](/tc39/proposal-pipeline-operator/blob/main/HISTORY.md). This is an official announcement thread for significant changes to the proposal’s explainer or spec. These will include things...

announcement

Quoting from [Hack pipes might be simpler to use](https://github.com/tc39/proposal-pipeline-operator#hack-pipes-might-be-simpler-to-use) > For example, with Hack pipes, value |> someFunction + 1 is invalid syntax and will fail early. There is no...

question
documentation

Heya hey, everyone. I’m a member of the TC39 pipe champion group, and I’m also a volunteer moderator here. I wanted to make an announcement. (It shouldn’t actually affect things...

announcement