What is the best way to support? about proposal-pipeline-operator HOT 15 CLOSED

If you have more feedback about the draft spec I wrote up, that could be very helpful. See #52 .

from proposal-pipeline-operator.

Is it possible to use/implement in typescript?

from proposal-pipeline-operator.

Use it in projects?
https://github.com/SuperPaintman/babel-plugin-syntax-pipeline

from proposal-pipeline-operator.

checkout: https://github.com/AirDwing/esnext-pipeline-biolerplate

from proposal-pipeline-operator.

@tomByrer you say that, but the bind proposal has been in babel for like 2 years and its no-where to be seen. ;(

from proposal-pipeline-operator.

@MeirionHughes already support checkout the project i just push

from proposal-pipeline-operator.

I was replying to Tom. Not to be pedantic, but babel support !== esnext. As I mentioned, the bind operator is also supported by babel, actively used in projects, and has been for a few years. But the proposal is no-where near getting into the next es version as far as I can see. :(

@freMea basically, it needs a tc39 champion to push it onto the agenda. see #33

from proposal-pipeline-operator.

I put it on the agenda last meeting, but we ran out of time. it's back on the agenda for the next meeting.

from proposal-pipeline-operator.

@Ebuall Those are two very different questions. For use, I don't think it's available. To implement, if I were maintaining TypeScript, I'd be a bit skeptical of this proposal as it hasn't been presented to TC39 yet. cc @DanielRosenwasser

from proposal-pipeline-operator.

@littledan I mean something like babel plugin + vscode extension

from proposal-pipeline-operator.

@Ebuall I don't know about the world of vscode extensions, but there's a Babel plugin at https://github.com/SuperPaintman/babel-plugin-transform-pipeline . It doesn't implement this exact spec, though.

from proposal-pipeline-operator.

More like cautious - but still extremely supportive and enthusiastic about the proposal. 😄

from proposal-pipeline-operator.

"Use it in projects?" Actually i do so https://github.com/madnight/githut i use the | syntax but that should be the same as |> as far as i understand.

Example:

createSeries(data) {
        const nonLang = new NonLangStore().getConfig()
        return data
            | reject(o => includes(o.name)(nonLang.lang))
            | take(10)
            | map(d => ({
                name: d.name,
                data: map('count')(filter({'name': d.name})(data))
            }))
            | uniqBy('name')
            | sortBy('name')
    }

I use this syntax for function chaining now for over one year in this project and from my experience i never had any issues with it. Its way easier (and more fun) to use than other compose methods and i think it should be part of the offical javascript syntax. So i can recommend you to give it a try if you haven't already.

from proposal-pipeline-operator.

@madnight that looks awesome.

I was a bit cautious and didn't want to use syntax which may look alien to newcomers so I developed https://github.com/egeozcan/ppipe . I wish I could get rid of the parentheses, and I have an experiment here: https://github.com/egeozcan/pppipe (yes there is an extra p :) ) and without that eval hack, that would have been awesome.

I would be very glad if anyone shared some thoughts.

from proposal-pipeline-operator.

Closing this issue, as the proposal has advanced to stage 2 with Hack-style syntax.

from proposal-pipeline-operator.