Closed (fixed)
Project:
Version Control API
Version:
6.x-1.0-beta5
Component:
Commit Log
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
30 Mar 2009 at 10:46 UTC
Updated:
15 Apr 2014 at 22:25 UTC
Jump to comment: Most recent
Comments
Comment #1
jpetso commentedThis week I'm too busy to do Version Control API work, but this stuff is easy as cooking Palatschinken: The cvs.module compatibility module in the CVS backend does pretty much exactly the same thing, so all that's needed is to copy-n-paste some code from that module and adapt the menu paths and menu callback names. Then submit a patch, and you're done!
I'd prefer if the path also contains the filter name so that filters other than the repository are possible too, e.g. "commitlog/repo/1", "commitlog/uid/56020", or "commitlog/id/33031".
Comment #2
neptunix commentedPancakes seems to be much easier for me, sorry :(
If I was familiar with drupal syntax :(
Comment #3
jpetso commentedOk ok ok, here you are: implemented in commit #191308.
This must be the most straightforward feature request I ever implemented for Version Control API. (Not that there were that many feature requests yet.)
It reuses hook_commitlog_constraints() so every (singular) constraint that works with request attributes (e.g. "repo", "id", "uid", "message", ...) will work as path argument after "commitlog". Only a single filter is possible though. As schemed in my previous comment, the path for a repository is consequently "commitlog/repo/[repo_id]".
Will appear in the release after 6.x-1.0-beta5 (I think that will be a release candidate already).
Comment #4
neptunix commentedGot cvs version. Works great. However using commitlog/id/123 does not make sense when you have more then one repository (as it always uses shows commits from the first repo). Anyway, thanks!