I think we should do it. The disadvantages aren't really disadvantages, since users could just write their own JSON-processing module if we don't give them one, and then those could both be issues anyway.
Jackmcbarn On Tue, Nov 4, 2014 at 3:45 PM, Brad Jorsch (Anomie) <bjor...@wikimedia.org> wrote: > There's a long-standing request for Scribunto to provide library functions > for JSON encoding and decoding. > > The advantage of this would be improved interoperability with the growing > number of extensions that use JSON (e.g. JsonConfig, Graph). > > The disadvantages include: > * People may store data in JSON blobs that must be parsed where a module > using mw.loadData would be more appropriate. > * People may write templates that attempt to bypass the normal MediaWiki > parameter handling mechanism in favor of passing a JSON blob, which would > likely lead to page wikitext that is harder for end users to understand. > > So, let's discuss it: do the advantages outweigh the potential > disadvantages? Are there additional advantages or disadvantages not yet > mentioned? > > > -- > Brad Jorsch (Anomie) > Software Engineer > Wikimedia Foundation > _______________________________________________ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
