We've just published a series of 17 (!) posts on common patterns in JSON Schema; lots of these have been culled from questions asked in the JSON-Schema Slack channel.
They are written from the perspective of .NET developers who are used to JSON serialization as a code-first exercise, and want to migrate towards schema-first (with generated code examples from Corvus.JsonSchema).
My latest pet #project: Replace the "free" #location sharing services with simple solution where one has full control of (a) data collection (b) data storage (c) data sharing/visualisation.
If you want to give this #GoogleLatitude like alternative a go, I'd be happy for any and all comments:
JSON is usually beautifully simply and useful. I'm starting to see the same un-necessarily over-complicated nesting of simple data by API vendors as the XML crowd. All I'm missing is Base64encoded JSON inside of Base64encoded JSON.
New WTF?!? that has me wanting to thwack an API providers team:
In one place it needs (without quotes)
"invoiceTotal": 17.37,
In another it needs; (with quotes)
"invoiceTotal": "17.37",
but if I pass 17.37 (bare) to PHPs json_encode it wraps it in quotes. I can't use JSON_NUMERIC_CHECK because it breaks the things that should be strings like "01" instead of 1.
There are kludgy work arounds... or I can hand code my JSON, but WTF?!?
TIL about the #WordPress Block Data API - used for retrieving block editor posts structured as #JSON data, with integrations for both the official WordPress REST API and #WPGraphQL.
Primarily designed for use in decoupled WordPress.
I wasn't aware until now, that jq is actually a full blown functional programming language. Originally it was inspired by Haskell and the very first version(s) of jq were actually implemented in Haskell. Only later jq got ported over to C. To have an idea how powerfull the jq language is, there is also a jq implementation purely written in jq: https://github.com/wader/jqjq#jq#json
I know that #json was never initially designed for configuration, but is there anything out there that actually works better for nested configuration settings? #yaml seems unsafe and easy to break, and #toml is simple but doesn't handle the nesting well. Perhaps nested configs are just a bad idea and we should stick with #toml?
I post a lot of sample code on this blog. My CodePen is full of little snippets of this and that. Quite often, these snippets need data to do something useful. A good example of that is my Lit example from this past week. Coming up with that data can be complicated, though. That is why I created a site for assorted test data. If you want to have a little rummage through it, I also made the git repository public for the site. While I was at it, I also put it behind a Cloudflare proxy to speed it up a little.
Have any questions, comments, etc? Please feel free to drop a comment below.
After the release of JSON Canvas, I was curious how people handle whiteboarding and graphical notes in Obsidian. Personally, I only use Excalidraw because I was already a user of its web version and because of its support for md and iframes, although I don't like how it handles embedded notes, everything else is easily corrected...
I need some help with #powershell where we need to export some #json values all as strings. So the numbers we have in the object need to be strings, but only are exported as integers.
I want to make a web app for viewing, creating, and modifying entries saved to a local file. I will use it on my old budget Android phone, and I want it to be as performant as I can possibly make it.
@cvennevik …And, in case you do decide to go this route, to make it easier for you, I just added .json() and .jsonFile() response helpers to the response objects passed to Kitten routes :)
@jamesog thanks for sharing this! I’m going to have to play with it. I have some complex #JSON cases that might really benefit. I also see promise in cases where today I might translate #XLSX to #CSV and then import into #SQLite. Why do all that if I can query the original directly? Awesome!
"JSON Patch is a format for describing changes to a #JSON document. It can be used to avoid sending a whole document when only a part has changed. When used in combination with the #HTTP PATCH method, it allows partial updates for HTTP #APIs in a standards compliant way."
#Bebop is a binary serialization repo, much faster than #json and supports many languages, including #Rust. The documentation also appears to have been created with #Astro, just a nice touch.
Do you use Excalidraw, Canvas, both or neither?
After the release of JSON Canvas, I was curious how people handle whiteboarding and graphical notes in Obsidian. Personally, I only use Excalidraw because I was already a user of its web version and because of its support for md and iframes, although I don't like how it handles embedded notes, everything else is easily corrected...