Opened at 2013-03-14T17:54:03Z
Last modified at 2013-03-15T05:37:42Z
#1930 new defect
should ?t=rename be deprecated in favour of ?t=move ?
| Reported by: | davidsarah | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | soon |
| Component: | code-frontend-web | Version: | 1.9.2 |
| Keywords: | cleanup web rename move | Cc: | |
| Launchpad Bug: |
Description (last modified by davidsarah)
In #1732 we added a ?t=move operation to the web-API, which is strictly more general than ?t=rename. Should we deprecate the latter?
(I tend towards keeping ?t=rename.)
Change History (4)
comment:1 Changed at 2013-03-14T17:54:23Z by davidsarah
- Description modified (diff)
comment:2 Changed at 2013-03-14T17:57:10Z by zooko
comment:3 follow-up: ↓ 4 Changed at 2013-03-15T05:34:31Z by davidsarah
Well, I suppose we can only deprecate it after we've changed tahoe mv to stop using it, in any case.
comment:4 in reply to: ↑ 3 Changed at 2013-03-15T05:37:42Z by davidsarah
Replying to davidsarah:
Well, I suppose we can only deprecate it after we've changed tahoe mv to stop using it, in any case.
I was mistaken, tahoe mv uses ?t=uri to add the link to the new location. It probably should be changed to use ?t=move, though.
Note: See
TracTickets for help on using
tickets.
I tend towards deprecating ?t=rename, because I like minimalism in an API and I think of every API function as another thing that slows down our progress because we have to support it. So I'm about +½ on deprecating it at this point.