#390: Product wiki syntax
-------------------------+-------------------------------------------------
Reporter: olemis | Owner: olemis
Type: task | Status: accepted
Priority: major | Milestone:
Component: | Version:
multiproduct | Keywords: product resource wiki syntax
Resolution: | TracLinks
-------------------------+-------------------------------------------------
Comment (by gjm):
Replying to [comment:7 andrej]:
> Replying to [comment:6 olemis]:
> [...]
> > - The solution is smart when expanding nested (i.e. product: ,
global:) TracLinks
> > expressions containing whitespaces . For instance the equivalent
of this link
> > `search:"foo bar"` will be `global:"search:foo bar"` or
> > `product:"PREFIX:search:foo bar"` instead of `global:"search:\"foo
bar\""` .
> > More examples in the test cases.
> Search is not resource and I suggest to have search always global. If
user want specify product, syntax may look like:
{{{search:?q=trac+link&product=xxx}}} similar to existing legacy search
syntax e.g.: {{{search:?q=trac+link&wiki=on}}}
Although it is not a true resource, would we naturally expect a search
link specified on a product ticket or wiki page to be searching globally?
It might be an edge case but it does change the scope of such a search if
it is an imported product and we are overriding the existing search
syntax.
Is the search page not going to be available under a product url?
Anyway, I am prepared to accept that this is just an occasional annoyance
that users can fix as long as they can work out how.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/390#comment:8>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
