If the elixir parser can be augmented to ignore the last trailing comma in a list literal like what Perl does, we can just blindly copy/paste the line.
derek-zhou
dimitarvp
dimitarvp
Awesome work putting this together, man. 
I did roughly the same with a shell script incantation:
mix hex.info ecto_sql | grep 'Config:' | sed 's/.*{\(.*\)}[^}]*/{\1},/'
Which yields:
{:ecto_sql, "~> 3.6"},
One can easily alias this in their shell startup file like I just did in my ~/.zshrc:
function _mix_hex_latest() {
mix hex.info $1 | grep 'Config:' | sed 's/.*{\(.*\)}[^}]*/{\1},/'
}
alias mix_hex_latest='_mix_hex_latest'
6
lud
The parser is already capable of doing this. The trailing comma is required so we can paste anywhere.
1
egze
Maybe an additional flag could do it?
mix hex.info jason --config
And it would just output
{:jason, "~> 1.2"}
6
kenny-evitt
Supporting a deps.json wouldn’t be that hard.
Most people (?) are using a single deps/0 function now that just returns a list of tuples.
It’d be easy enough to parse a JSON file and return a list of ‘deps’ tuples. Your tool’s README could just document how users would modify their deps/0 function to included the parsed JSON output, e.g. something like:
defp deps do
[
# Fixed/static/hard-coded deps (if any) ...
]
++ function_or_something_with_parsed_deps_json_data()
end
Personally, I don’t like npm-style ‘add deps’ CLI commands – I much prefer maintaining deps ‘manually’ as-is the current convention.
1
opsb
Been writing elixir daily for 5 years and did not know there were any mix hex tasks… Just discovered mix hex.search as well (doesn’t give you a tuple but does give you the latest version number).
2
wojtekmach
Hex Core Team
You can also do:
$ curl --silent https://hex.pm/api/packages/jason | jq -r '.configs."mix.exs"'
{:jason, "~> 1.2"}
which is what mix hex.info does under the hood 
8
mindok
Yikes. Remember WORM drives (write once, read many) - sed & perl are more like WORN - write once, read never.
2