Opened 21 years ago
Last modified 10 years ago
#1200 new enhancement
Provide syntax to link to file-differences from svn log messages
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | low | Milestone: | next-major-releases | 
| Component: | version control/changeset view | Version: | 0.8 | 
| Severity: | normal | Keywords: | wiki custom syntax | 
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
It would be nice if there was a syntax for filenames in svn log messages, so that the filename in question becomes a link that jumps to the corresponding file in the diff.
Attachments (0)
Change History (9)
comment:1 by , 21 years ago
| Priority: | normal → low | 
|---|
comment:2 by , 20 years ago
comment:3 by , 20 years ago
| Owner: | changed from to | 
|---|---|
| Status: | new → assigned | 
I wonder if this can be handled by adding a "catch all" regexp to the wiki engine, which could be used to do an optional, context-dependent, parse step.
In this case, the Changeset module could build a lambda that tries to identify the relevant filenames from the changelog text.
This way, even the mention of a README file could be catched, because we can build the regexp from the list of changes files.
comment:4 by , 20 years ago
| Status: | assigned → new | 
|---|
comment:5 by , 19 years ago
| Keywords: | wiki custom syntax added | 
|---|---|
| Milestone: | → 0.11 | 
comment:6 by , 19 years ago
| Milestone: | 0.11 → 0.12 | 
|---|
Probably not for 0.11, though the WikiEngine refactoring is done having the requirements for this ticket in mind.
comment:7 by , 15 years ago
| Milestone: | next-major-0.1X → unscheduled | 
|---|
comment:8 by , 15 years ago
| Milestone: | unscheduled → next-major-0.1X | 
|---|
The idea I had with this is that one should be able to easily add some kind of post-processing to the WikiDom tree, for adding contextual rules.
e.g. here, a dynamic pattern made of the list of files in the (restricted) changeset, (using shortest non-ambiguous paths) and targeting the local changes (#fileX).
comment:9 by , 10 years ago
| Owner: | removed | 
|---|



  
This is related to #124 (not a duplicate though).