move command should take destination as a relative path too for local operation

[satra]

running the following command moves the file from the current directory into the root directory of the dandiset. this seems unintuitive for a unix user.

/mnt/beegfs/Lee/dandi/sub-MITU01/ses-20211016h18m33s42/micr$ dandi move sub-MITU01_sample-100_photo.jpg sub-MITU01_ses-20211016h18m33s42_sample-100_photo.jpg

[yarikoptic]

hm, indeed seems sensible to expect both source and destination paths to be relative to current directory. Or we are missing some usage pattern which would contradict that @jwodder ?

[yarikoptic]

note: I have retitled to be closer to the underlying UX issue. The original title was "behaves different from unix move" but to answer that one - even though we aimed to stay close to "unix move" semantic in the design of dandi move, because we are to operate on both local and remote instances within one command, we might not be able to mimic "unix move" exactly, so we are likely to behave differently and that would be ok IMHO.

[satra]

seems like this expects the user to know many things. let's simplify it to either take a prefix (e.g., dsroot://), or perhaps give a prompt that says this will move it location X, are you sure? someone could use --yes if they didn't want a prompt.

[yarikoptic]

seems like this expects the user to know many things.

like what? is dandi move --help too complicated and/or interface too non-intuitive?

Please file those ideas as separate issues to discuss and possibly implement. In this one I think we should address the original problem first since IMHO it goes not inline with what dandi move --help says

 In addition, when running the command inside a subdirectory of a
  Dandiset, all paths must be relative to the subdirectory, even if only
  operating on the remote Dandiset.

and thus I consider it a bug.

[satra]

i filed this as a user experience issue rather than a bug (but it is also a bug). i would still say its also user experience issue.

[github-actions]

🚀 Issue was released in 0.45.1 🚀

[yarikoptic]

i filed this as a user experience issue rather than a bug (but it is also a bug). i would still say its also user experience issue.

and hopefully we improve user experience having fixed the bug ;)