Is there a way to asign the stream to a variable?

[ganlanyuan]

No description provided.

[rask]

Please elaborate, do you want to read a YAML file in your Gulpfile into a variable while running a task?

[ganlanyuan]

Yes, I need pase the yaml file as a variable to another task.
I can transfer yaml to json, and get the data as a variable from json file, but that's one more step and also get an unnecessary json file.
If you can help, that will be great!
Thanks

[rask]

So in essence you have Task 1 that reads a YAML and the YAML should be available to a Task 2?

I think this is bad practise and you should just read the YAML again in Task 2, as the Task 2 might sometimes run without Task 1 running before it, which might break the system.

If you just need to read YAML config to be a global config for all tasks then there are libraries for that.

[ganlanyuan]

Sorry I didn't make it clear.
Actually I want to get the variable within the same task, not another task.

If you just need to read YAML config to be a global config for all tasks then there are libraries for that.

It's just JavaScript data, not for configuration.

[rask]

I see, so first you'd read the YAML data, then use the YAML data in a following pipe step? I quite certain there already was a Gulp plugin for this but I'll see whether I have the time to see how this could be implemented. If you have any ideas then please do create a pull request. :)

[ganlanyuan]

I see, so first you'd read the YAML data, then use the YAML data in a following pipe step?

Yes.
I searched, but couldn't find a good solution.

[rask]

I can try to find some time to see how to implement this neatly, no promises. Please, let me know if you stumble upon a solution that works for you so I can see how they have implemented it. :)

[ganlanyuan]

Okay, thanks a lot for considering this

…

On Mon, Mar 20, 2017, 7:44 AM Otto Rask ***@***.***> wrote: I can try to find some time to see how to implement this neatly, no promises. Please, let me know if you stumble upon a solution that works for you so I can see how they have implemented it. :) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AExGmwPn69mv8EkY9qCQCjnep4Y2zKqzks5rnmasgaJpZM4Mg3MH> .