In order for people to write JSON templates, we need a JSON filter. This is an extensibility mechanism. JSON output is clearly desired and desirable - I've got one use case myself, and it's the way the web is going. The JSON-RPC interface isn't yet mature enough to meet all the needs people will have, and the BzAPI isn't yet part of core Bugzilla, so let's make it easier for them to get JSON out in other ways until one of those things becomes true. It's eight lines of code implementing the escaping rules for a frozen spec, and it will need no maintenance. Given the low risk and general usefulness, I think it's worth taking this into the core rather than making every extension provide it as a template-before_process hook. Gerv
Created attachment 414061 [details] [diff] [review] Patch v.1
Assignee: general → gerv
Status: NEW → ASSIGNED
Attachment #414061 - Flags: review?(mkanat)
Comment on attachment 414061 [details] [diff] [review] Patch v.1 No, I'm sorry, but we don't take code we aren't using, and this could be easily added by an extension, using the template_before_create hook.
If we start including JSON code in Bugzilla itself, then we'd have a use for this and we'd want to include it.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.