Ticket #740 (closed defect: fixed)

Opened 2 years ago

Last modified 23 months ago

Changecommentlink/revlink should take project/repo into consideration

Reported by: marcusl Owned by: marcusl
Priority: major Milestone: 0.8.0
Version: master Keywords: jinja
Cc:

Description

We must the changecommentlink/revlink properties to WebStatus? so that they handle project/repository input as well. (doesn't make much sense otherwise... ;)

I'll try to fix that in the near time.

Change History

comment:1 Changed 23 months ago by marcusl

  • Status changed from new to closed
  • Resolution set to fixed

(In [b466c5d4bccbe13ea2d6d94169d452526a3404bc]):

WebStatus?: Add support for project and repository in changecommentlink/revlink

  • These WebStatus? args can now be callables, dicts or (as before) a single string/tuple
  • Added projectlink/repolink that adds URLs to repo/project main pages
  • Changed jinja change_macro to take a change as arg (cleaner code)
  • Changed some support classes in console to take a single build/sourcestamp arg instead of picking every necessary variable
  • The revlink/shortrev/changecomment filters now take a parameter, the repo or project to which the revision/comment belongs.
  • Shorten all revs to 40 chars in html rather than in python.
  • Add unit test for jinja link filters

Comments belong to projects as they usually refer to ticket ids. So project == ticket db.

Note: See TracTickets for help on using tickets.