status: change "changed checksum" state to "changed command"

[jorgeorpinel]

Report

Extracted from iterative/dvc.org#1384 (review)

The changed checksum status (which only applies to .dvc files, mostly for backward compatibility purposes) should be called something else probably, maybe changed command. Something that reflects better what the change or state is.

Please provide information about your setup

DVC 1.1

[jorgeorpinel]

P/s addressing this will imply a small change to the status cmd ref in the docs.

[efiop]

The changed checksum status (which only applies to .dvc files, mostly for backward compatibility purposes) should be called something else probably, maybe changed command. Something that reflects better what the change or state is.

There is no command in .dvc files created by add and import[-url]. So current changed checksum still makes sense. 🙂

[jorgeorpinel]

OK. But .dvc files no longer store their own checksums, right?

Also, the term we use now is "file hash" (or sometimes "hash value" to avoid repeating the word "file" depending on the context). checksum was deemed inaccurate, and refers only to HDFS external deps/outs now.

P/s I opened this issue per your iterative/dvc.org#1384 (comment), Ruslan 🙂 so up to you if you want to close it.

[efiop]

OK. But .dvc files no longer store their own checksums, right?

dvc import[-url]ed do store checksums.

Also, the term we use now is "file hash" (or sometimes "hash value" to avoid repeating the word "file" depending on the context). checksum was deemed inaccurate, and refers only to HDFS external deps/outs now.

Yeah, this is a bigger issue all over the code. It will be solved gradually.

P/s I opened this issue per your iterative/dvc.org#1384 (comment), Ruslan slightly_smiling_face so up to you if you want to close it.

Thanks! Closing since the terminology is correct here (with exception of checksum, but that is to be solved in the future just gradually).