Add support for tables

[NEO97online]

Table from modules/Hash_Table.jai is empty when parsing typed JSON, it would be great to have support for loading arbitrary data as a Table.

[rluba]

Can you give me a concrete example of what you want to parse into what? I want to make sure I understand your problem correctly.

[NEO97online]

@rluba sure thing.

Given this JSON:

{
	"name": "Consolas",
	"char_widths": {
		"!": 3,
		"I": 3
	}
}

I want to parse it into a struct like this:

Font :: struct {
    name: string;
    char_widths: Table(u8, int);
}

The way I'm handling it without first-class support for tables is by doing this:

FontJsonData :: struct {
    name: string;
    char_widths: JSON_Value;
}

And I load it as FontJsonData, then I transform it like this:

    if font_data.char_widths.type == .OBJECT {
    	for font_data.char_widths.object {
    		if it.type == .NUMBER {
    			table_add(*font.char_widths, it_index[0], cast(int) it.number);
    		} else {
    			print("[load_computer_font] char_widths fields should all be numbers!");
    			return false, .{};
    		}
    	}
    } else {
	print("[load_computer_font] char_widths should be an object!");
	return false, .{};
    }

So I would imagine a similar parsing code to populate a Table built into the library, similar to what is done for dynamic arrays.

[berdal84]

@rluba If you accept contributions, I may give a try to implement the missing Table feature and submit a PR.

[rluba]

@berdal84 Sure, give it a try!

[J-Chris-Findlay-RESIDEO]

Slightly related - I've seen parsers that allow a catch-all field to be created (in this case of type JSON_Value) where unknown fields get put. That might be a nifty feature to have here too as it allows for gradual extension more easily. Does this need its own issue?

[rluba]

That’s totally unrelated to this feature but also an interesting suggestion.

[J-Chris-Findlay-RESIDEO]

Ok, I'll make it its own suggestion (c: