[tahoe-lafs-trac-stream] [tahoe-lafs] #1732: consider changes to webapi "Move" API before release

[tahoe-lafs]

#1732: consider changes to webapi "Move" API before release
-------------------------------+-------------------------------------------
     Reporter:  warner         |      Owner:  warner
         Type:  enhancement    |     Status:  new
     Priority:  critical       |  Milestone:  1.10.0
    Component:  code-          |    Version:  1.9.1
  frontend-web                 |   Keywords:  forward-compatibility blocker
   Resolution:                 |
Launchpad Bug:                 |
-------------------------------+-------------------------------------------

Comment (by ClashTheBunny):

 My personal feeling is that this API would benefit from having a total
 compatibility with rename such that if rename were deprecated in the
 future, it would be a one word change from 'rename' to 'relink'.  You
 could even do it with a hex editor on a binary since it's the same number
 of bits.  I don't care as much about things being optional as I care about
 things being compatible.  If we require to_dir, if people want to jump
 from rename to relink, that much more work will be required and that much
 more chance of people messing up.

 Philosophically, I'm for APIs that easy to use, but only if they are
 unambiguous and easy to not misuse.  I don't think that having either
 to_dir or to_name be required makes the API ambiguous or easy to misuse.
 A good programmer with an attention to details would probably fill them
 both in anyhow.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1732#comment:43>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage