Mercurial > p > roundup > code
view website/issues/html/msg.index.html @ 5192:302e3a1a7190
Three sets of changes:
1) Make sure that a user doesn't create a query with the same name
as an existing query that the user owns.
2) When submitting a new named query, display the name of the query
on the index page.
3) Allow optional arguments to indexargs_url by setting their value
to None. This will show the argument only if there is a valid
value.
To match these, changed the template for all search templates so if an
error is thrown due to #1 the user stays on the search page so they
can fix the issue.
Note that I did not add automated tests for these because I couldn't
find existing tests for these code paths that I could adapt. I don't
understand how the existing Action tests work and there is no doc for
them.
| author | rouilj@uland |
|---|---|
| date | Wed, 08 Mar 2017 22:04:15 -0500 |
| parents | c2d0d3e9099d |
| children |
line wrap: on
line source
<tal:block metal:use-macro="templates/page/macros/icing"> <title metal:fill-slot="head_title" i18n:translate="" >List of messages - <span tal:replace="config/TRACKER_NAME" i18n:name="tracker"/></title> <span metal:fill-slot="body_title" tal:omit-tag="python:1" i18n:translate="">Message listing</span> <td class="content" metal:fill-slot="content"> <table tal:define="batch request/batch" class="messages"> <tr><th colspan=3 class="header" i18n:translate="">Messages</th></tr> <tal:block tal:repeat="msg batch"> <tr> <th><a tal:attributes="href string:msg${msg/id}"><tal:x replace="msg/id"/></a></th> <th tal:content="string:Author: ${msg/author}">author</th> <th tal:content="string:Date: ${msg/date}">date</th> </tr> <tr> <td colspan="3"><pre tal:content="msg/content">content</pre></td> </tr> </tal:block> <metal:block use-macro="templates/issue.index/macros/batch-footer" /> </table> </td> </tal:block>