You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might become very valuable, especially for UX, if code (now) provisions what version(s) of the layout it currently supports (i.e., 1 ATM), and then announces if it detects layout version it does not support. We do already something similar in case installed datalad detects metadata which that version does not support (yet) and instructs user to upgrade: https://github.com/datalad/datalad/blob/c077fac5600c5aeeac65c529f914e3baa0d8ae02/datalad/metadata/metadata.py#L814
TODO here seems only to include supported versions in annex info ORA-REMOTE. If there's an unknown version we have a message announcing this. Wording of that message needs to be better, but it's there and (by default) the special remote would still try to read but refuse to write. This is because a different version may still have the relevant keys for an operation at the same location as the default version of the special remote - so we can try. But we don't want to write to possibly wrong locations w/o requiring the user to explicitly say "I know what I'm doing".
Came up in the review of datalad/datalad#4459, citing @mih:
It might become very valuable, especially for UX, if code (now) provisions what version(s) of the layout it currently supports (i.e., 1 ATM), and then announces if it detects layout version it does not support. We do already something similar in case installed datalad detects metadata which that version does not support (yet) and instructs user to upgrade: https://github.com/datalad/datalad/blob/c077fac5600c5aeeac65c529f914e3baa0d8ae02/datalad/metadata/metadata.py#L814
Ref also datalad/datalad#4410
The text was updated successfully, but these errors were encountered: