-
-
Notifications
You must be signed in to change notification settings - Fork 42
Open
Description
How do you feel about jet
having a config file where certain default options/preferences can be specified?
What's the benefit?
For example input and out formats by default are EDN. But what if you happen to work with JSON more as the default input format, could there be a way to specify that the default format should be JSON?
One way I figured that this could be implemented is by having a config file where you could specify the default input format.
It could be something like ~/.jet.edn
the config could look like:
{:from :json
:to :json}
So that instead of typing:
echo "some JSON payload" | jet -i json -f "#(foo bar %)" -t json
it could be typed as:
echo "some JSON payload" | jet -f "#(foo bar %)"
Where the :from
& :to
options would be read from ~/.jet.edn
.
a13
Metadata
Metadata
Assignees
Labels
No labels