analyzing is hard when using merged resume

[oupala]

When using merged resume, analyzing becomes hard as it seems not possible to use more than one json file.

It could be a good idea to allow analyzing merged resume:

hackmyresume ANALYZE in1.json in2.json

[hacksalot]

Perhaps a bit different syntax to distinguish from analyzing multiple resumes. We have this pesky requirement that all commands should operate on multiple files. So, to analyze multiple resumes:

hackmyresume ANALYZE r1.json r2.json r3.json

To merge and analyze a single resume from its constituent parts:

hackmyresume ANALYZE a.json b.json c.json --merge

Or maybe:

hackmyresume ANALYZE a.json | b.json | c.json

Or then again

hackmyresume ANALYZE a.json < b.json < c.json

For that matter we could extend this syntax to all commands allowing for ad hoc resume merging and flowing in any command context.

[oupala]

This seems ok.

My preference goes to the first proposal, as the --merge parameter is the most explicit.

hackmyresume ANALYZE a.json b.json c.json --merge

Could we use parenthesis to group files?

hackmyresume ANALYZE (a.json b.json) (a.json c.json)

So that hackmyresume analyses a and b merged, then a and c merged also. It allows multiple groups to be analyzed at the same time.

[zachdecook]

hackmyresume merge a.json b.json | hackmyresume analyze -

The merge command should read in multiple files and output a single merged file. This is then piped into the analyze command (which should read from /dev/stdin if the given filename is -)