#390: Product wiki syntax
-------------------------+-------------------------------------------------
Reporter: olemis | Owner: jure
Type: task | Status: review
Priority: major | Milestone:
Component: | Version:
multiproduct | Keywords: product resource wiki syntax
Resolution: | TracLinks
-------------------------+-------------------------------------------------
Changes (by olemis):
* status: accepted => review
* owner: olemis => jure
Comment:
I submitted [attachment:t390_r1450181_product_wikisyntax_report.diff
another patch] extending report compact syntax in the following ways
1. Retry `{ns 1}` links when `ns` is not an InterTrac prefix
2. `{product:PREFIX 1}` , `{product:PREFIX:1}`, `{global:1}`
2. `product:"PREFIX:{1}"` , `product:"PREFIX:{1}"`, `global:"{1}"` (<=
QUOTED ;)
3. `{PREFIX~1}` , `PREFIX~{1}` ... where `~` is product syntax delimiter
(see comment:)
{{{
#!sh
$ hg qapplied
t390/t390_r1453952_product_wikisyntax.diff
t390/t390_r1453952_product_ticket_jira.diff
t390/t390_r1453952_product_wikisyntax_nomatch.diff
t390/t390_r1453952_product_wikisyntax_compact.diff
t390/t390_r1450181_product_wikisyntax_report.diff
t434/t434_r1453952_product_ticketquery.diff
$ hg log -r qparent --template="[{svnrev}] - {desc}\n"
[1455129] - #429 - Multiproduct UI: Ticket page (modify ticket was not
working)
$ python setup.py test -m tests.wikisyntax
[...]
----------------------------------------------------------------------
Ran 222 tests in 52.724s
OK
}}}
IMO , this is all we need . If something is wrong or missing then feel
free to reopen this ticket , though I'll recommend to spawn another one
from this point .
PS: Later today you'll get a report of the full test suite . Until
yesterday it was quite green , the only exception being the case mentioned
in comment:14
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/390#comment:16>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
