In #244 we clarified the correct login code paths in various documentations, and made the unsupported/incorrect paths error clearly and plainly.
It seems preferable, though, to follow the Brew model, of correcting the user, pausing, and then doing what they meant. (In this case, we DO know what they meant.)
- n.b. we MUST clarify-and-wait before proceeding, or else we risk causing anxiety in the user, making them wonder whether the different commands are indeed the same.
Acceptance Criteria
Issuing a datumctl auth login results in a warning message telling the user that datumctl login is the supported path, then a two-second wait, then following the datumctl login code path.
In #244 we clarified the correct login code paths in various documentations, and made the unsupported/incorrect paths error clearly and plainly.
It seems preferable, though, to follow the Brew model, of correcting the user, pausing, and then doing what they meant. (In this case, we DO know what they meant.)
Acceptance Criteria
Issuing a
datumctl auth loginresults in a warning message telling the user thatdatumctl loginis the supported path, then a two-second wait, then following thedatumctl logincode path.