JSON - Revision history

M at 18:32, 6 September 2021

2021-09-06T18:32:12Z

← Older revision		Revision as of 18:32, 6 September 2021
Line 32:		Line 32:

	==== Examples ====		==== Examples ====
	~~use these:~~		===== constructors =====

	~~// CONSTRUCTING~~
	object j;		object j;
	j["my-name"] = "Heisenburg";		j["my-name"] = "Heisenburg";
	j["my-number"] = 42;		j["my-number"] = 42;

			// initialization list
	object jv =		object jv =
	{		{
Line 58:		Line 58:
	}		}
	};		};

	// ~~PARSING~~		// string literal
			string strThing = R"(
			{
			"name": "blah",
			"number": 123
			}
			)";
			object jThing = parse( strThing );

			===== Parsing =====
	object jBody = parse(payload).as_object();		object jBody = parse(payload).as_object();
	if ( !jBody.if_contains( "sub" ) \|\| !jBody.if_contains( "role" )) return;		if ( !jBody.if_contains( "sub" ) \|\| !jBody.if_contains( "role" )) return;
Line 73:		Line 82:
	ss << j;		ss << j;
	string strMyJ = serialize( j );		string strMyJ = serialize( j );

	~~==== String literals for hardcoded JSON ====~~
	* You can use C++ string literals for hardcoded JSON, easier to read than the initializer list squiggly-bracket nightmare:
	~~R"(~~
	{
	~~"name": "blah",~~
	~~"number": 123~~
	}
	~~)";~~

	==== Library history ====		==== Library history ====

M: /* Warnings */

2021-09-06T16:03:06Z

Warnings

← Older revision		Revision as of 16:03, 6 September 2021
Line 5:		Line 5:

	==== Warnings ====		==== Warnings ====
	~~NOTE~~ YOU CAN'T USE `using namespace boost::json` without ~~fuckign~~ up std::string!		* YOU CAN'T USE `using namespace boost::json` without fucking up std::string! Arrogant boost author decided his string was better - fine - but name it something else you ass.
			* You can't extract easily from a const object with brackets (it [https://www.boost.org/doc/libs/1_77_0/libs/json/doc/html/json/ref/boost__json__object/operator_lb__rb_.html has no const version] because it returns a reference). What bullshit.
			# Nope, not gonna work, you can't use [] on a const object, durrr...
			string order = jMsg["client_order_id"].as_string().c_str();
			# Workaround one liner
			string order = jMsg.at("client_order_id").as_string().c_str();

	==== Header ====		==== Header ====

M: /* Header */

2021-09-06T15:49:47Z

Header

← Older revision		Revision as of 15:49, 6 September 2021
Line 10:		Line 10:
	when we need nlohmann:		when we need nlohmann:

	using ~~namespace~~ nlohmann::json;		using nlohmann::json;

	when we need boost:		when we need boost:

M: /* String literals for hardcoded JSON */

2021-09-06T15:39:22Z

String literals for hardcoded JSON

← Older revision		Revision as of 15:39, 6 September 2021
Line 70:		Line 70:

	==== String literals for hardcoded JSON ====		==== String literals for hardcoded JSON ====
	* You can use C++ string literals for hardcoded JSON, easier to read than squiggly ~~constructor thingee~~:		* You can use C++ string literals for hardcoded JSON, easier to read than the initializer list squiggly-bracket nightmare:
	R"(		R"(
	{		{

M: /* Library history */

2021-09-06T15:38:03Z

Library history

← Older revision		Revision as of 15:38, 6 September 2021
Line 81:		Line 81:
	* rapidjson: I started with this. It is brutally low-level and cumbersome (fast? not to develop against...).		* rapidjson: I started with this. It is brutally low-level and cumbersome (fast? not to develop against...).
	* nlohmann: This was great to code with. Very elegant and straightforward. I moved towards boost to get better performance and a library with "more eyeballs". But this is still used by quicktype, which is used by my Postgres template code, which is really nice... and even tho quicktype is kinda dead... I'm keeping it for as long as I can.		* nlohmann: This was great to code with. Very elegant and straightforward. I moved towards boost to get better performance and a library with "more eyeballs". But this is still used by quicktype, which is used by my Postgres template code, which is really nice... and even tho quicktype is kinda dead... I'm keeping it for as long as I can.
	* boost: I started using boost::json on boost v 1.77, when it seemed to be generally not insane (like its predecessor spirit was...). It's slightly cumbersome, not that bad, and hopefully will get better.		* boost: I started using boost::json on boost v 1.77, when it seemed to be generally not insane (like its predecessor property_tree/spirit/bleh was...). It's slightly cumbersome, not that bad, and hopefully will get better.

M: /* String literals for hardcoded JSON */

2021-09-06T15:30:45Z

String literals for hardcoded JSON

← Older revision		Revision as of 15:30, 6 September 2021
Line 70:		Line 70:

	==== String literals for hardcoded JSON ====		==== String literals for hardcoded JSON ====
	* ~~Use~~ C++ string literals for hardcoded JSON ~~whenever possible~~:		* You can use C++ string literals for hardcoded JSON, easier to read than squiggly constructor thingee:
	R"(		R"(
	{		{

M at 15:29, 6 September 2021

2021-09-06T15:29:25Z

@@ Line 4: / Line 4: @@
 We will use boost::json wherever possible.  Keep updating it, and move to c++ std json if it becomes a thing.  We still use nlohmann for quicktype and postgres-jsonb.
-* Configuration
+==== Warnings ====
      NOTE YOU CAN'T USE `using namespace boost::json` without fuckign up std::string!
-* Usage:
+==== Header ====
      when we need nlohmann:
@@ Line 26: / Line 26: @@
          auto jBars = jResponse["bars"].as_array();
 * Use C++ string literals for hardcoded JSON whenever possible:
          R"(

M at 15:27, 6 September 2021

2021-09-06T15:27:05Z

← Older revision		Revision as of 15:27, 6 September 2021
Line 2:		Line 2:

	=== C++ ===		=== C++ ===
	We will use boost::json wherever possible. Keep updating it, and move to c++ std json if it becomes a thing.		We will use boost::json wherever possible. Keep updating it, and move to c++ std json if it becomes a thing. We still use nlohmann for quicktype and postgres-jsonb.

	```		* Configuration
			NOTE YOU CAN'T USE `using namespace boost::json` without fuckign up std::string!

			* Usage:
	when we need nlohmann:		when we need nlohmann:

	using namespace nlohmann::json;		using namespace nlohmann::json;

	when we need boost:		when we need boost:

	// boost/json.hpp		// boost/json.hpp
	using boost::json::~~value~~;		using boost::json::object; // << most common!
	using boost::json::array;		using boost::json::array;
	using boost::json::~~object~~;		using boost::json::value; // << avoid, too generic
	using boost::json::value_from;		using boost::json::value_from;
	using boost::json::parse;		using boost::json::parse;
	using boost::json::serialize;		using boost::json::serialize;
	using boost::json::kind;		using boost::json::kind;
	~~```~~
			// OR: Use auto to short-circuit the bullshit whenever possible.
			auto jBars = jResponse["bars"].as_array();

			* Use C++ string literals for hardcoded JSON whenever possible:
			R"(
			{
			"name": "blah",
			"number": 123
			}
			)";

	==== Library history ====		==== Library history ====

M: Created page with "JSON is as simple as possible but no less. Genius. === C++ === We will use boost::json wherever possible. Keep updating it, and move to c++ std json if it becomes a thing...."

2021-09-06T15:22:12Z

Created page with "JSON is as simple as possible but no less. Genius. === C++ === We will use boost::json wherever possible. Keep updating it, and move to c++ std json if it becomes a thing...."

New page

JSON is as simple as possible but no less. Genius.

=== C++ ===
We will use boost::json wherever possible. Keep updating it, and move to c++ std json if it becomes a thing.

```
when we need nlohmann:

using namespace nlohmann::json;

when we need boost:

// boost/json.hpp
using boost::json::value;
using boost::json::array;
using boost::json::object;
using boost::json::value_from;
using boost::json::parse;
using boost::json::serialize;
using boost::json::kind;
```

==== Library history ====
* rapidjson: I started with this. It is brutally low-level and cumbersome (fast? not to develop against...).
* nlohmann: This was great to code with. Very elegant and straightforward. I moved towards boost to get better performance and a library with "more eyeballs". But this is still used by quicktype, which is used by my Postgres template code, which is really nice... and even tho quicktype is kinda dead... I'm keeping it for as long as I can.
* boost: I started using boost::json on boost v 1.77, when it seemed to be generally not insane (like its predecessor spirit was...). It's slightly cumbersome, not that bad, and hopefully will get better.