Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What do you think of a config file? #84

Open
dotemacs opened this issue Apr 4, 2021 · 2 comments
Open

What do you think of a config file? #84

dotemacs opened this issue Apr 4, 2021 · 2 comments

Comments

@dotemacs
Copy link
Contributor

dotemacs commented Apr 4, 2021

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.

@borkdude
Copy link
Owner

borkdude commented Apr 4, 2021

Could be useful eventually, but I would like to wait for some more feedback/upvotes on this one. If people would like to change the defaults they could also make a bash alias:

alias jetj='jet -i json -o json' 

@dotemacs
Copy link
Contributor Author

dotemacs commented Apr 4, 2021

Could be useful eventually, but I would like to wait for some more feedback/upvotes on this one.

That's fair.

If people would like to change the defaults they could also make a bash alias:

alias jetj='jet -i json -o json' 

I guess that :from & :to are very short options and I get that shell aliases suffice for that example.

Let's see how do others feel about this.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants