deprecate one of the synonyms "/file/" and "/named/" from the WAPI #1903
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1903
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
[webapi.rst]source:docs/frontends/webapi.rst?rev=05d0b8b5b9247e1d0541e58250a81df89d5c9115#viewing-downloading-a-file says: "URLs may also use /file/$FILECAP/FILENAME as a synonym for /named/$FILECAP/FILENAME.". Why is that? Let's deprecate "/file/".
Review needed: https://github.com/tahoe-lafs/tahoe-lafs/pull/29
remove one of the synonyms "/file/" and "/named/" from the WAPIto deprecate one of the synonyms "/file/" and "/named/" from the WAPIReview comments on github. BTW, [FileHandler in web/root.py]source:src/allmydata/web/root.py@880af4e1#L92 should probably be renamed to
NamedHandler
and the error messages in it changed to reference/named
, in that case.source:src/allmydata/web/info.py#L143 and source:src/allmydata/web/directory.py (lines 733, 743, and 1042) use
/file
. Nothing currently uses/named
.In my opinion
/named
is a better word for this API than/file
, since the difference between/file
and/uri
is not that the former is a file and the latter isn't.OK, +1 for that pull request modulo https://github.com/tahoe-lafs/tahoe-lafs/pull/29#commitcomment-2387217, but let's also have a patch for comment:90786, comment:90787, and to change any uses of
/file
in tests to/named
.I'm adding the tag "
forward-compatibility
" because we want to ship a stable release with this deprecation in place before shipping a future stable release with the deprecated API removed.I'm still not sure why we're deprecating "/file" which is used, rather than deprecating "/named" which is unused. (I value having fewer redundant options but I'm not sure it really matters what they are called.)
Replying to daira:
I wanted to move to "/named" because it explains what it actually does — it changes the name of the downloaded file. Calling this feature "/file" is confusing because it is still a file even if you don't use this feature.
OK, then this needs the changes in comment:90789, which probably means that the deprecation isn't going to get into 1.11.
In 3e73461/trunk:
In afb7718/trunk:
Oops, I didn't notice the commit's auto-closing comment. I didn't mean to mark this one fixed yet.. I just wanted to land some old PRs.
To resolve this ticket, I think we need more changes (stop using /file, etc).
moving most tickets from 1.12 to 1.13 so we can release 1.12 with magic-folders
Moving open issues out of closed milestones.
Ticket retargeted after milestone closed