Zig

Demonstrates how to Handle Large Integers in JSON

See more JSON Examples

Demonstrates how to handle large integers in JSON. (Integers larger than what can fit in a 32-bit signed integer.) Zig

const std = @import("std");
const chilkat = @import("chilkat");

pub fn main(init: std.process.Init) !void {
    const alloc = init.arena.allocator();

    // Let's say your JSON has this:

    // {
    //     "id": 20000000001234567
    // }

    const json = try chilkat.JsonObject.init();
    defer json.deinit();

    json.loadFile("qa_data/json/large_int.json") catch {
        std.debug.print("{s}\n", .{try json.getLastErrorText(alloc)});
        return;
    };

    // The integer is too large for a 32-bit signed integer that is returned by IntOf.
    // The result will be something that wrapped around and could be negative.
    // In this case it would be: -543893881
    const id = json.intOf("id");
    std.debug.print("id: {d}\n", .{id});

    // The solution is to read the integer value as a string, and then use the features in your programming language
    // to convert from a string to a 64-bit integer.
    //
    // Alternatively, you may wish to simply hold the value as a string.  If, for example, the integer simply references
    // an order ID, an account ID, etc., then there's no need to convert to an integer value.  You're not going to be doing
    // mathematical operations on it anyway.  This is usually the case for large integers -- they typically exist
    // in JSON as an account ID.

    // You can get any JSON value as a string:
    const account_id = try json.stringOf(alloc, "id");
    std.debug.print("accountId: {s}\n", .{account_id});

    // Sample output:

    // id: -543893881
    // accountId: 20000000001234567
}