Opened 19 years ago
Last modified 10 years ago
#2168 closed enhancement
Universal TracLinks argument — at Version 11
Reported by: | Christian Boos | Owned by: | Christian Boos |
---|---|---|---|
Priority: | normal | Milestone: | 0.11 |
Component: | wiki system | Version: | devel |
Severity: | minor | Keywords: | traclinks |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
Currently, each flavor of TracLinks implements its own "sub" syntax.
There is some consistency however, for example, a trailing "#fragment" is used to locate a specific anchor in the targeted objects. This works for section anchors in Wiki pages and more recently for line numbers in repository files.
Also, there's some support for the special "?format=raw" argument which works for attachment: links, and it was suggested that source: links adopt the same convention.
What becomes apparent from the above is that those conventions are pretty much the same as those used for URIs.
Therefore, I propose to add the query URI syntax to the TracLinks syntax, for the short and long form of links (but not for the shorthand forms).
Examples:
- source:trunk/README?format=txt Access the README file in "text" mode
- wiki:WikiStart?format=txt Access the WikiStart page in "text" mode
- log:trunk?limit=10 See the last ten changesets on trunk
- query:?milestone=1.0&owner=cboos See my 1.0 tickets (works already)
- search:?q=google&wiki=on Search for "google" in Wiki pages (works already)
- report:14?PRIORITY=highest … works in Trac > r2322
Change History (11)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
Milestone: | → 0.9.1 |
---|
See also #2078, for a similar request concerning changeset: links.
comment:3 by , 18 years ago
Milestone: | 0.9.1 → 0.9.2 |
---|
comment:4 by , 18 years ago
Milestone: | 0.9.3 → 1.0 |
---|
comment:5 by , 18 years ago
See also #2635 for a discussion about uniform handling of
versioning arguments (e.g. type:id@version
for addressing
a specific version of the object, and type:id@versionx:versiony
for addressing a specific change or group of changes for the object).
follow-up: 7 comment:6 by , 18 years ago
Milestone: | 1.0 → 0.11 |
---|
We should also allow fragment identifiers after tickets (e.g. ticket:2168#comment:5 or #2168#comment:5) and changesets (e.g. r1231#file3, see #2078).
comment:7 by , 18 years ago
Replying to cboos:
We should also allow fragment identifiers after tickets (e.g. ticket:2168#comment:5 or #2168#comment:5) …
How funny, I just wanted to write a comment here saying just that… again!
I find the current comment link syntax (e.g. comment:ticket:3555:5) a bit irritating… It was initially modelled after the attachment syntax (e.g. attachment:<resource>:<file>
), but in the case of comments, it's really annoying to have to split the comment:
prefix and the comment number.
Maybe we could change both syntaxes to thing:which_thing:type:id
?
Ideally, this could even be "recursive", e.g. comment:4:attachment:the_file.txt:ticket:345
.
Just brainstorming…
comment:8 by , 18 years ago
(side-note: the syntax changes suggested in comment:7 were implemented in [3824:3828])
comment:9 by , 17 years ago
comment:10 by , 17 years ago
Keywords: | TracLinks added |
---|
comment:11 by , 17 years ago
Description: | modified (diff) |
---|---|
Status: | new → assigned |
See also #1209, for a similar request concerning milestone: links.