element.py: Fix consistency of workspaced elements when ref is missing

Fixes #393 (closed).

I like how existence of the workspace on disk is used here to determine consistency.

I wonder if Consistency.INCONSISTENT (usually taken to mean we have no clue even what it is) is the right choice over Consistency.RESOLVED (taken to mean we know what it is, but we just dont have it)

I think I like your choice here, we cannot really ever know what it is, if it is a workspace.

This might however have a side effect of the user might get suggested "Hey, we dont know what this is, how about you try bst track on this element ?", then again I guess the same would be true regardless of the choice of INCONSISTENT or RESOLVED - lets deal with those edge cases separately, there are probably some error messages which need to change for inconsistent workspaced elements.

marked as a Work In Progress

added 11 commits

• 6e718c02...e023beb5 - 9 commits from branch master
• ecc1d074 - element.py: Fix consistency of workspaced elements when ref is missing
• b35ee809 - fixup! element.py: Fix consistency of workspaced elements when ref is missing

Compare with previous version

added 1 commit

• 00230948 - fixup! fixup! element.py: Fix consistency of workspaced elements when ref is missing

Compare with previous version

added 1 commit

• ba6eaba6 - element.py: Fix consistency of workspaced elements when ref is missing

Compare with previous version

unmarked as a Work In Progress

resolved all discussions

resolved all discussions

added 2 commits

• 84a57b2f - 1 commit from branch master
• 314c25d8 - element.py: Fix consistency of workspaced elements when ref is missing

Compare with previous version

enabled an automatic merge when the pipeline for 314c25d8 succeeds

merged