#include <iostream> #include <nlohmann/json.hpp> using json = nlohmann::json; int main() { // create JSON values json j_null; json j_boolean = true; json j_number_integer = 17; json j_number_float = 23.42; json j_object = {{"one", 1}, {"two", 2}}; json j_object_empty(json::value_t::object); json j_array = {1, 2, 4, 8, 16}; json j_array_empty(json::value_t::array); json j_string = "Hello, world"; // call empty() std::cout << std::boolalpha; std::cout << j_null.empty() << '\n'; std::cout << j_boolean.empty() << '\n'; std::cout << j_number_integer.empty() << '\n'; std::cout << j_number_float.empty() << '\n'; std::cout << j_object.empty() << '\n'; std::cout << j_object_empty.empty() << '\n'; std::cout << j_array.empty() << '\n'; std::cout << j_array_empty.empty() << '\n'; std::cout << j_string.empty() << '\n'; }

January 20, 2025 - The page you requested cannot be displayed (HTTP response code 403)

I'm developing an API and need to be able to output empty arrays and objects in the returned JSON. However, I'm running into a problem where empty objects/dicts are returned as empty arrays. Example Request Body: { "attributes": { "empty_array": [], "empty_object": {} } } Actual Response: { "attributes": {

March 3, 2022 - Loading · ×Sorry to interrupt · Refresh

April 24, 2022 - SELECT data FROM courses WHERE JSON_EXTRACT(data, '$.codes') = JSON_ARRAY(); Bingo! The result was as expected! +---------------------------------------+ | data | +---------------------------------------+ | {"name": "Pharmacology", "codes": []} | | {"name": "Toxicology", "codes": []} | +---------------------------------------+ 2 rows in set (0.01 sec) SELECT data FROM courses WHERE JSON_LENGTH(data, '$.codes') = 0; The result as expected, only return records with empty codes

How to send a empty array to JSON request to the API?

In contrast to regular arrays from the BDL, the elements of a JSON array can be of different data types. The following data types are allowed for JSON arrays: [ ] //Empty JSON array [ 0, 1, 2, 3, 4, 5] [ “StringValue”, 10, 20.13, true, null ] [ { “Name” : “Nested Object” }, [ 10, 20, true, 40, “Nested Array” ] ]

February 14, 2025 - The “empty array issue” in JSON requests usually refers to a situation where your server-side code (e.g., in PHP, Python, Node.js, etc.) is receiving an empty array ([]) in the request body when you expect it to contain data.

February 7, 2025 - Change "SomeConfiguration:SomeArray" from being set to null to being set to "", an empty string. And now the array "handler" essentially works like the string "handler" that does differentiate between null and "" (though the problem there is that "" is not the same as [] in JSON either, but I might be the only one concerned with that...)

September 8, 2016 - I imagine it may have to do with safe values, however this causes confusion and headaches when third party consumers of my service are expecting, for instance, an object but gets an array. Can Services View be updated so that for empty values:

January 12, 2020 - I have a structure I'm trying to deserialize into JSON to send elsewhere · Some of the fields in this structure are lists of objects. When <List>.Empty == true, Outsystems supposedly initializes a single empty object with all default values. This is what I want to serialize

October 21, 2019 - I stepped through each line, and used the local mapper object to serialise an empty array at every step. This revealed the culprit pretty quickly: ... By default, Micronaut sets the serializationInclusion value to JsonInclude.NON_EMPTY, which omits empty objects/arrays from JSON to save space.

Loading · ×Sorry to interrupt · Refresh

November 4, 2023 - In our application, we consume external services. The JSON request which we send to the external API has empty arrays tagged.

May 5, 2017 - Loading · ×Sorry to interrupt · Refresh

April 5, 2020 - Anyone knows how to check an json array is empty? I have gathered a few json arrays but some of them are empty, could anyone advise me how to verify if any json array is empty? Regards, Victor