Native JSON functions

ID:1982708
 
Nov 15 2015, 2:45 am
Resolved
To improve communication with browser controls and especially the webclient, JSON now has native support. The two new procs, json_encode() and json_decode(), can be used to convert between BYOND values and JSON. (Please note: Datums are not serialized with json_encode(); they are converted to their text output equivalent.)
Applies to:DM Language
Status: Resolved (510.1320)
This issue has been resolved.
So, as far as I can tell, the server and the webclient use json in some fashion to communicate.

So my thinking, (if the above is true) is that since DD has to already have some json parsing functions, opening access to those up would be super handy. mostly because it could avoid 5 gazillion string tree lookups pledging the ones we use.

Just some simple jsonEncode and jsonDecode procs, having it go to jagged arrays (lists of lists) or from.

We already use json in ss13 as the communication between the auto updating JS based rich interfaces and the server, but it's performance is kinda lacking, mainly because the string tree is a thing.
Nov 15 2015, 10:30 am
Good idea.
Nov 15 2015, 2:21 pm
Would be nice to have for our config files as well! :+1:
Nov 15 2015, 5:18 pm
In response to Lummox JR
While you're looking at JSON stuff, ?format=json for hub stuff as well pretty-please?
Nov 15 2015, 5:46 pm
In response to Murrawhip
Murrawhip wrote:
While you're looking at JSON stuff, ?format=json for hub stuff as well pretty-please?

https://jsonformatter.curiousconcept.com/
http://codebeautify.org/jsonviewer
http://jsonprettyprint.com/
http://jsonformat.com/
Nov 25 2015, 1:40 pm
In response to A.T.H.K
That helps... How?
Nov 25 2015, 4:04 pm
In response to Murrawhip
Murrawhip wrote:
That helps... How?

You'd only want a "pretty" version to be able to make it human readable, you don't need pretty for production... Therefore, I gave you a few simple sites that'll make it human readable for your testing.
Nov 25 2015, 5:11 pm
I believe he means he wants a json format output for the hub urls, not that the json needs to be pretty.

is that something that already exists?
Nov 25 2015, 5:12 pm
They said "pretty-please" not that he wanted pretty json format.

They were hoping for a way to have the format of the hub urls to be json for easy parsing
Nov 25 2015, 5:37 pm
In response to Optimumtact
Optimumtact wrote:
I believe he means he wants a json format output for the hub urls, not that the json needs to be pretty.

is that something that already exists?

My mistake, read it wrong obviously.
Nov 30 2015, 9:57 pm
Just to make you aware, json_encode() and json_decode() are on the list for 510.
Jan 27 2016, 11:41 am
Lummox JR resolved issue with message:
To improve communication with browser controls and especially the webclient, JSON now has native support. The two new procs, json_encode() and json_decode(), can be used to convert between BYOND values and JSON. (Please note: Datums are not serialized with json_encode(); they are converted to their text output equivalent.)