[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:
         Type:  defect             |     Status:  new
     Priority:  normal             |  Milestone:  1.10.0
    Component:  code-frontend-web  |    Version:  1.9.1
   Resolution:                     |   Keywords:  forward-compatibility
Launchpad Bug:                     |
-----------------------------------+-----------------------------------
Changes (by davidsarah):

 * keywords:   => forward-compatibility
 * type:  task => defect


Comment:

 I agree as well (in general I don't like overloading of the interpretation
 of one argument based on another argument, in any API).

 Should {{{to_dircap}}} accept a path after the dircap? Note that
 supporting that would allow changing {{{tahoe mv}}} to use this API, which
 is a prerequisite to fixing #973 in the way proposed in
 ticket:973#comment:4 (since that fix depends on knowing the path that was
 used in the {{{tahoe mv}}} command to specify the destination). If it does
 accept a path then it should be called something other than
 {{{to_dircap}}}.

 Unix {{{mv}}} can rename a file at the same time as moving it. Should
 there be a {{{to_name}}} argument (defaulting to {{{from_name}}})?

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