Details
Description
gives the following examples:
<configuration>
<resolutionIds>Closed</resolutionIds>
<statusIds>Resolved, Closed</statusIds>
<typeIds>Bug, New Feature, Improvement, Wish</typeIds>
</configuration>
However, spaces are not always allowed, they can cause the field to be ignored.
<statusIds>Resolved,Closed</statusIds> - OK
<statusIds> Resolved,Closed</statusIds> - OK
<statusIds>Resolved,Closed </statusIds> - OK
<statusIds> Resolved,Closed </statusIds> - OK
<statusIds>Resolved, Closed</statusIds> - Closed is ignored
<statusIds> Resolved, Closed</statusIds> - Closed is ignored
<statusIds> Resolved, Closed </statusIds> - Closed is ignored
In particular, the example from the web page does not work.
Note that the typeIds field does appear to allow leading space after a comma.
The resolutionIds field does not.
Since spaces are sometimes allowed, may I suggest the code is fixed rather than the documentation?
r1131414 | bimargulies | 2011-06-04 11:17:46 -0400 (Sat, 04 Jun 2011) | 4 lines
[MCHANGES-254, MCHANGES-253] add more calls to trim, fix doc.
Also fix some warnings in site generation.