Dear list,
I noticed that both /usr/bin/rt and RT::Interface::REST do not support
whitespace in attribute names. However, whitespace is allowed in Custom
field. Take, for instance, rt.cpan.org:
CF-Severity: Critical
CF-Broken in: 0.05
CF-Fixed in:
The problem is with $field variable, which is set to
‘[a-zA-Z][a-zA-Z0-9_-]*’
One solution is to allow whitespace for custom fields:
‘(?:[a-zA-Z][a-zA-Z0-9_-]|CF-[a-zA-Z0-9_ -])’
Another solution is to disallow whitespace in custom fields. My point
is, REST should be consistent with RT rules, otherwise it becomes
unusable. (Try doing ‘edit’ on CPAN RT tickets).
Comments?
Dear list,
I noticed that both /usr/bin/rt and RT::Interface::REST do not support
whitespace in attribute names. However, whitespace is allowed in Custom
field. Take, for instance, rt.cpan.org:
CF-Severity: Critical
CF-Broken in: 0.05
CF-Fixed in:
The problem is with $field variable, which is set to
‘[a-zA-Z][a-zA-Z0-9_-]*’
One solution is to allow whitespace for custom fields:
‘(?:[a-zA-Z][a-zA-Z0-9_-]|CF-[a-zA-Z0-9_ -])’
I’d take a patch to do this. Thanks
Dear list,
I noticed that both /usr/bin/rt and RT::Interface::REST do not support
whitespace in attribute names. However, whitespace is allowed in Custom
field. Take, for instance, rt.cpan.org:
CF-Severity: Critical
CF-Broken in: 0.05
CF-Fixed in:
The problem is with $field variable, which is set to
‘[a-zA-Z][a-zA-Z0-9_-]*’
One solution is to allow whitespace for custom fields:
‘(?:[a-zA-Z][a-zA-Z0-9_-]|CF-[a-zA-Z0-9_ -])’
I’d take a patch to do this. Thanks
I don’t have 3.6.0 installed, so I can’t test against the latest. I can
make a patch for 3.4.5 (looks like rt and RT::Interface::REST haven’t
changed), and you merge it?
I don’t have 3.6.0 installed, so I can’t test against the latest. I can
make a patch for 3.4.5 (looks like rt and RT::Interface::REST haven’t
changed), and you merge it?
Drop me the patch and I’ll have a look?
I don’t have 3.6.0 installed, so I can’t test against the latest. I can
make a patch for 3.4.5 (looks like rt and RT::Interface::REST haven’t
changed), and you merge it?
Drop me the patch and I’ll have a look?
It’s allready in the repository, revision 5652.
–
List info: The rt-devel Archives
Best Practical is hiring! Come hack Perl for us: Careers — Best Practical Solutions
Best regards, Ruslan.