You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently --template and --stdin are mutually exclusive.
In other words, you can use --template:
$ node cli.js --template 'How about some {red.bold chocolate} & {blue.bold peanut butter}?'
How about some chocolate & peanut butter?
and you can use data from stdin:
$ echo 'How about some chocolate & peanut butter?' | node cli.js --stdin yellow
How about some chocolate & peanut butter?
but you can't use --template with data from stdin:
$ echo 'How about some {red.bold chocolate} & {blue.bold peanut butter}?' | node cli.js --template --stdin
Input required
I think it would be cool if this were possible. The last example with echo is a little silly because it can so easily be changed to the first command, but imagine if the "chalk markup" string were a lot longer and it were in a file, say chocolate-and-peanut-butter.chalk.txt and then you could do:
I agree it would be useful to support this, but I also think it's weird that --template then can both accept a value and also be used as a boolean flag for stdin. I think we should then make it only a boolean flag and make the template always come as stdin or the first argument.
Currently
--template
and--stdin
are mutually exclusive.In other words, you can use
--template
:and you can use data from stdin:
but you can't use
--template
with data from stdin:I think it would be cool if this were possible. The last example with
echo
is a little silly because it can so easily be changed to the first command, but imagine if the "chalk markup" string were a lot longer and it were in a file, saychocolate-and-peanut-butter.chalk.txt
and then you could do:The text was updated successfully, but these errors were encountered: