toJSON incorrectly stringifies object

[Grafu]

Describe the bug

When serializing a standalone object, the returned JSON puts it into an array. This is incorrect because the object is not in an array before serialization. An argument for correct behavior should solve the problem.

To reproduce

srun outputChatBox(toJSON ( { "dogs", cat = "hungry", mouse = "food", birds = 4 } ))

Expected behaviour

Command results: { "1": "dogs", "mouse": "food", "cat": "hungry", "birds": 4 } [string]

Actual behaviour

Command results: [ { "1": "dogs", "mouse": "food", "cat": "hungry", "birds": 4 } ] [string]

This should only be triggered by:
toJSON ( { { "dogs", cat = "hungry", mouse = "food", birds = 4 } } )

Version

MTA:SA Server v1.5.6-release-16345
Multi Theft Auto v1.5.6-release-18706

[patrikjuvonen]

Indeed we need a new argument for this correct behavior.

[dmi7ry]

Also I would like to have abillity to disable json optimisation

[qaisjp]

JSON optimisation?

[dmi7ry]

If there are same tables, toJSON() may store them as links on the first table, it looks like ... ,"^T^9","^T^9","^T^9", ... ,"^T^15" etc.

[qaisjp]

If there are same tables, toJSON() may store them as links on the first table, it looks like ... ,"^T^9","^T^9","^T^9", ... ,"^T^15" etc.

This seems like a bug and should only happen for self-referencing tables. Please can you create a separate issue for this?

i.e. this should not happen:

run a = { this = "that" }
run toJSON({ alpha = a, beta = a })
[16:19:52] Command results: [ { "alpha": { "this": "that" }, "beta": "^T^1" } ] [string]

Relevant: e883f1c

mtasa-blue/Server/mods/deathmatch/logic/lua/CLuaArgument.cpp

Lines 811 to 825 in e11685c

	case LUA_TTABLE:
	{
	ulong* pTableId;
	if (pKnownTables && (pTableId = MapFind(*pKnownTables, m_pTableData)))
	{
	// Self-referencing table
	char szTableID[10];
	snprintf(szTableID, sizeof(szTableID), "^T^%lu", *pTableId);
	return json_object_new_string(szTableID);
	}
	else
	{
	return m_pTableData->WriteTableToJSONObject(bSerialize, pKnownTables);
	}
	}

(and the corresponding client file).

[dmi7ry]

I'm exactly about self-referencing tables.
So it would be useful, for example, if I need later edit the result by hands (in DB), or work with it on web, etc.

[qaisjp]

It is not possible to represent self-referencing tables in JSON

[dmi7ry]

I want it just writes a copy of the table instead of the link to it. Something like this:

run a = { this = "that" }
run toJSON({ alpha = a, beta = a }, true, "none", true ) -- last `true` to diable references on tables
[16:19:52] Command results: [ { "alpha": { "this": "that" }, "beta": { "this": "that" } } ] [string]

[patrikjuvonen]

But how would a copy work? It's an infinite loop or I'm missing something?

Nevermind. Seems like something we should add an option for.

I propose we change toJSON to accept an options table with the current option arguments and add a new one named maybe useReferencing (?) (default: true).

[qaisjp]

I actually think it's a bug and only meant to be for truly self-referencing (recursive) tables — in this case I think we should fix the ^T happening without any args.

[Pirulax]

No shit, so thats what is causing MTA's famous double array JSON.. I see..
FYI the whole CLuaArgument class is bad as a whole.
I wanted to refactor it, but i got brain damage.