Just show the runtime dependencies. They are listed in the JSON under dependencies: { runtime: [ ] }, so a hash with runtime as the key, and it is an array that can be empty or have content.
Now, how to output them... that's the question. I suspect we would add them to the end of the output per gem, and then just do indented newlines with the name and requirementsexample:
The emoji could be 🗃️ [Emojipedia Link]. It may need to be repeated if separate lines are used, otherwise spacing could be an issue. Will play that by ear.
Just show the runtime dependencies. They are listed in the JSON under
dependencies: { runtime: [ ] }
, so a hash withruntime
as the key, and it is an array that can be empty or have content.Example:
As for the flag, probably
-d
/--dependencies
.Now, how to output them... that's the question. I suspect we would add them to the end of the output per gem, and then just do indented newlines with the
name
andrequirements
example:Example:
The emoji could be 🗃️ [Emojipedia Link]. It may need to be repeated if separate lines are used, otherwise spacing could be an issue. Will play that by ear.