[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 davidsarah):

 Replying to [comment:43 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.

 Well, if that were a concern then we could just not deprecate
 {{{rename}}}. It's not really imposing significant complexity, since it
 will be implementable by delegating to {{{relink}}}.

 I'm with warner: -0 on having either {{{to_dir}}} or {{{to_name}}} be
 optional. Do we have concensus on the comment:39 spec then? If so I will
 start implementing it tomorrow.

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