tree 12a7bb1fdad779beab837a645ce24041750c7195
parent 9c9cdba45dba1e898e3b169858e56d344dc85831
author Marcel van Lohuizen <mpvl@golang.org> 1587460680 +0200
committer Marcel van Lohuizen <mpvl@golang.org> 1587624497 +0000

cmd/cue/cmd: merge data files by default

This also harmonizes handling of schema versus data.

The distinction between data and schema is not always
clear. Yet the cue command makes a notable distinction
on how the two are handled and even varied behavior
based on whether the two were mixed or not.

Also, there was a difference in behavior based on CUE
vs JSON files: CUE files were merged in a single package,
whereas JSON files were printed one-by-one.

Advantages:
- less distinction between different formats
- merge JSON files on the command line
- merge schema and data on the command line

There are a few exceptions:
- cue vet still validates data files individually
- schema are separated when the -d flag is used.

The latter is kind of an eye sore and we probably need
a different approach selecting schema.

Change-Id: I4d61b363d4ad08f4d0cfb1fe4bdf4f15b106988e
Reviewed-on: https://cue-review.googlesource.com/c/cue/+/5745
Reviewed-by: Marcel van Lohuizen <mpvl@golang.org>