Accept STDIN

[huygn]

So we can chain with https://github.com/svg/svgo output.

[goopscoop]

Could you share more details about the changes you're proposing?

[huygn]

The idea is to have svgo optimize your SVG and then make a React component out of it in 1 command.

I'd love to be able to do smthing like this: svgo my.svg -o - > svgtoreact - MyCompopent.

[goopscoop]

The idea sounds good. Do you foresee this as being a breaking change?

[huygn]

Not as much imo, although I haven't looked into the source yet :D

On Wed, Jan 4, 2017, 12:51 AM Cody Barrus ***@***.***> wrote: The idea sounds good. Do you foresee this as being a breaking change? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#11 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKFF80gYQvPnDL5tGJJ0v2SmlexVYVqGks5rOoqqgaJpZM4LZm0h> .

-- Best regards, Huy Giang

[goopscoop]

I don't see a problem with this. In principle, this should allow us to pipe the output of any other tool into svgtoreact. As long as the application of this change allows for general piping indiscriminate from the source, then I'm on board. Thanks in advance for your contribution!

[huygn]

Great 👍

[cjke]

Really like the piping idea.

Curious how/if we should split the "dir" mode vs the single mode to better accomodate this. I don't have a concrete answer right now - but wanted to mention it. I'll try to think of some common approaches (for example, other command line utilities that deal with both single files but also process directories). I will also create a seperate issue for the single vs dir mode so this issue doesn't become clogged.