Improve templating

[twaugh]

The output template can now be more flexible, so that:

• the full output line can be controlled, rather than only the text after the package name
• the top-level package for a vendored package can be included in each output line

[mprahl]

Did you mean to make this html/template instead of text/template? html/template will escape HTML characters, which is likely undesired.

[twaugh]

Thanks! Nice catch. Fixed.

[mprahl]

Have you considered using an option to write to a JSON file with all this information and then the caller can programmatically parse the JSON file rather than pass in a template and then parse the output text of retrodep?

[mprahl]

👍 once the comments are considered

[twaugh]

Have you considered using an option to write to a JSON file with all this information and then the caller can programmatically parse the JSON file rather than pass in a template and then parse the output text of retrodep?

That's a good idea. In fact we could have a -o option similar to ocs, allowing:

• retrodep -o json ...
• retrodep -o go-template="{{...}}" ...

This new -o go-template= option could be the way to specify a full-line template (eliminating the need for -new-template), with -template providing compatibility for the previous templating style.

[twaugh]

I've updated it to use -o go-template=..., to allow -o json in the future. I took a quick stab at working out how to make JSON output work but ran into questions when dealing with unknown versions. I filed #97 to track that separately.

[vkrizan]

Looks good. Great idea of having more than one output format with -o.

[twaugh]

Updated README.md.

[vkrizan]

Please reflect argument changes to -o [go-template=...].

[twaugh]

Thanks, updated.

[mprahl]

👍