Consider renaming `version` in the config file?

[joelostblom]

Currently we have an option to check in the config called version which is referring to the version of the datapackage. I wonder if this might be confusing since --version generally refers to the version of the program itself.

# Outputs the version of cdp
cdp --version

# Specifies the version of the datapackage?
cdp check --version 1

Adding to the confusion is that cdp check --version currently works and seems to output the version of cyclopts (same for flower sucommands).

I am not sure what a good alternative name could be. Only verbose option comes to mind like --datapackage-version, --dp-version, --version-number, --spec-version, etc. Maybe --release, but it's ambiguous.

[lwjohnst86]

Good point. Hmm. I think spec is the most accurate. We could have spec for e.g. Data Package or data-dict.yaml (if it progresses)> And spec-version (or spec.version so it could be nested under [spec]?)

[joelostblom]

spec sounds good to me too. If me make it nested, would we also need a nested key like name or type for the name/type of the spec? E.g.:

[spec]
name = 'data-dict.yaml'
version = 0.1

vs

spec = 'data-dict.yaml'
spec_version = 0.1

Nested seems more structured, just wonder what the key would be named.

[lwjohnst86]

Yea, I like nested too. Can you do nested easily via the CLI? Just wondering how we could set the spec via the CLI if not doing within a project 🤔