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
One of git's bad UX habits is that when the current working directory is a submodule that is not present (unnitialized), it will execute its actions on the parent repository. I repeatedly had to explain this to my non-technical colleagues who did not understand error messages or datalad dropped all data from their main dataset by accident because the submodule was not there.
I think that when the current working directory is a subdataset which is not initialized, datalad should refuse to take any action other than datalad get, informing the user that they are in a subdataset which is not present. This would make datalad drop indempotent -- repeating datalad drop on a folder would give the same result regardless of whether I do it once or twice. In my opinion, this is what users expect.
What steps will reproduce the problem?
Create and save a subdataset
Drop that subdataset
cd into the folder of the subdataset
Execute any action, e.g. "datalad drop".
Expected: Datalad will tell the user that the current dataset has already been dropped. Other datalad commands except "get" might issue an error telling the user that they first need to "get" the dataset before taking any action on it
Actual behavior: Datalad will silently fall back to the superdataset. I can imagine no situation where the user would want that given that the current working directory is the subdataset
DataLad information
No response
Additional context
No response
Have you had any success using DataLad before?
No response
The text was updated successfully, but these errors were encountered:
What is the problem?
One of git's bad UX habits is that when the current working directory is a submodule that is not present (unnitialized), it will execute its actions on the parent repository. I repeatedly had to explain this to my non-technical colleagues who did not understand error messages or
datalad dropped
all data from their main dataset by accident because the submodule was not there.I think that when the current working directory is a subdataset which is not initialized, datalad should refuse to take any action other than
datalad get
, informing the user that they are in a subdataset which is not present. This would makedatalad drop
indempotent -- repeatingdatalad drop
on a folder would give the same result regardless of whether I do it once or twice. In my opinion, this is what users expect.What steps will reproduce the problem?
Expected: Datalad will tell the user that the current dataset has already been dropped. Other datalad commands except "get" might issue an error telling the user that they first need to "get" the dataset before taking any action on it
Actual behavior: Datalad will silently fall back to the superdataset. I can imagine no situation where the user would want that given that the current working directory is the subdataset
DataLad information
No response
Additional context
No response
Have you had any success using DataLad before?
No response
The text was updated successfully, but these errors were encountered: