ToJSON - Revision history

Fernando187: Remove obsolete Requirements section

2024-11-07T15:32:15Z

Remove obsolete Requirements section

← Older revision		Revision as of 15:32, 7 November 2024
Line 34:		Line 34:
	local json = toJSON ( { "dogs", cat = "hungry", mouse = "food", birds = 4 } )		local json = toJSON ( { "dogs", cat = "hungry", mouse = "food", birds = 4 } )
	</syntaxhighlight>		</syntaxhighlight>

	~~==Requirements==~~
	~~{{Requirements\|1.0\|1.1.1-9.03316\|}}~~

	==See Also==		==See Also==

Yeleha at 09:29, 12 July 2024

2024-07-12T09:29:07Z

← Older revision		Revision as of 09:29, 12 July 2024
Line 4:		Line 4:

	{{Important Note\|Due to technical limitations (partly of json-c) the stringified keys will be truncated to the first 255 characters}}		{{Important Note\|Due to technical limitations (partly of json-c) the stringified keys will be truncated to the first 255 characters}}
	{{ Warning\| When using [[toJSON]] for submitting data using [[fetchRemote]] for example, make sure to use string.sub(data, 2, -2) to remove the brackets as many APIs will not understand the request }}		{{ Warning\| When using [[toJSON]] for submitting data using [[fetchRemote]] for example, make sure to use '''string.sub(data, 2, -2)''' to remove the brackets as many APIs will not understand the request }}
	==Syntax==		==Syntax==
	<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd -->		<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd -->

Yeleha: Warning for using toJSON in requests.

2024-07-12T08:45:09Z

Warning for using toJSON in requests.

← Older revision		Revision as of 08:45, 12 July 2024
Line 4:		Line 4:

	{{Important Note\|Due to technical limitations (partly of json-c) the stringified keys will be truncated to the first 255 characters}}		{{Important Note\|Due to technical limitations (partly of json-c) the stringified keys will be truncated to the first 255 characters}}
			{{ Warning\| When using [[toJSON]] for submitting data using [[fetchRemote]] for example, make sure to use string.sub(data, 2, -2) to remove the brackets as many APIs will not understand the request }}
	==Syntax==		==Syntax==
	<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd -->		<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd -->

Srslyyyy: Fix typo.

2022-07-04T11:47:14Z

Fix typo.

← Older revision		Revision as of 11:47, 4 July 2022
Line 3:		Line 3:
	This function converts a '''single''' value (preferably a Lua table) into a [[JSON]] encoded string. You can use this to store the data and then load it again using [[fromJSON]].		This function converts a '''single''' value (preferably a Lua table) into a [[JSON]] encoded string. You can use this to store the data and then load it again using [[fromJSON]].

	{{Important Note\|Due to ~~tehnical~~ limitations (partly of json-c) the stringified keys will be truncated to the first 255 characters}}		{{Important Note\|Due to technical limitations (partly of json-c) the stringified keys will be truncated to the first 255 characters}}

	==Syntax==		==Syntax==

Pirulax: Add important note: keys will be truncated to 255 characters

2021-03-24T15:58:57Z

Add important note: keys will be truncated to 255 characters

← Older revision		Revision as of 15:58, 24 March 2021
Line 2:		Line 2:
	{{Server client function}}		{{Server client function}}
	This function converts a '''single''' value (preferably a Lua table) into a [[JSON]] encoded string. You can use this to store the data and then load it again using [[fromJSON]].		This function converts a '''single''' value (preferably a Lua table) into a [[JSON]] encoded string. You can use this to store the data and then load it again using [[fromJSON]].

			{{Important Note\|Due to tehnical limitations (partly of json-c) the stringified keys will be truncated to the first 255 characters}}

	==Syntax==		==Syntax==

StrixG: Add ru page

2019-01-12T18:57:24Z

Add ru page

← Older revision		Revision as of 18:57, 12 January 2019
Line 38:		Line 38:
	==See Also==		==See Also==
	{{Server_functions}}		{{Server_functions}}

			[[ru:toJSON]]

Myonlake at 11:33, 25 September 2018

2018-09-25T11:33:39Z

← Older revision		Revision as of 11:33, 25 September 2018
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	{{Server client function}}		{{Server client function}}
	~~{{New feature/item\|3.0120\|1.2\|\|~~
	~~Available client side in 1.2 and onwards.~~
	}}

	This function converts a '''single''' value (preferably a Lua table) into a [[JSON]] encoded string. You can use this to store the data and then load it again using [[fromJSON]].		This function converts a '''single''' value (preferably a Lua table) into a [[JSON]] encoded string. You can use this to store the data and then load it again using [[fromJSON]].

Line 10:		Line 6:
	<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd -->		<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd -->
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	string toJSON ( var value, [ bool compact = false ][, string prettyType = "none" ] )		string toJSON ( var value [, bool compact = false ][, string prettyType = "none" ] )
	</syntaxhighlight>		</syntaxhighlight>

Line 21:		Line 17:
	*'''compact:''' a [[boolean]] representing whether the string will contain whitespaces. To remove whitespaces from JSON string, use ''true''. String will contain whitespaces per default.		*'''compact:''' a [[boolean]] representing whether the string will contain whitespaces. To remove whitespaces from JSON string, use ''true''. String will contain whitespaces per default.
	}}		}}
	{{New feature/item\|3.~~0160~~\|1.6\|8046\|		{{New feature/item\|3.0154\|1.5.3\|8046\|
	*'''prettyType:''' a type [[string]] from below:		*'''prettyType:''' a type [[string]] from below:
	** none		** none

Qaisjp: tweak syntax

2016-07-30T13:51:39Z

tweak syntax

← Older revision		Revision as of 13:51, 30 July 2016
Line 10:		Line 10:
	<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd -->		<!-- NOTE: don't use 'special' names for variable names, e.g. you shouldn't be writing things like 'player player, vehicle vehicle', instead write something like 'player thePlayer, vehicle vehicleToGetInto'. This is less confusing and prevents the syntax highlighting being odd -->
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	string toJSON ( var value, [ bool compact = false ] )		string toJSON ( var value, [ bool compact = false ][, string prettyType = "none" ] )
	</syntaxhighlight>		</syntaxhighlight>

	~~{{New feature/item\|3.0160\|1.6\|8046\|~~
	~~<syntaxhighlight lang="lua">~~
	~~string toJSON ( var value, [ bool compact = false, string prettyType = "none" ] )~~
	~~</syntaxhighlight>~~
	}}

	===Required Arguments===		===Required Arguments===

Necktrox at 22:00, 29 July 2016

2016-07-29T22:00:07Z

← Older revision		Revision as of 22:00, 29 July 2016
Line 11:		Line 11:
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	string toJSON ( var value, [ bool compact = false ] )		string toJSON ( var value, [ bool compact = false ] )
	</syntaxhighlight>		</syntaxhighlight>

			{{New feature/item\|3.0160\|1.6\|8046\|
			<syntaxhighlight lang="lua">
			string toJSON ( var value, [ bool compact = false, string prettyType = "none" ] )
			</syntaxhighlight>
			}}

	===Required Arguments===		===Required Arguments===
Line 20:		Line 26:
	{{New feature/item\|3.0150\|1.5\|\|		{{New feature/item\|3.0150\|1.5\|\|
	*'''compact:''' a [[boolean]] representing whether the string will contain whitespaces. To remove whitespaces from JSON string, use ''true''. String will contain whitespaces per default.		*'''compact:''' a [[boolean]] representing whether the string will contain whitespaces. To remove whitespaces from JSON string, use ''true''. String will contain whitespaces per default.
			}}
			{{New feature/item\|3.0160\|1.6\|8046\|
			*'''prettyType:''' a type [[string]] from below:
			** none
			** spaces
			** tabs
	}}		}}

Audifire: /* Optional Arguments */

2015-06-11T21:38:35Z

Optional Arguments

← Older revision		Revision as of 21:38, 11 June 2015
Line 19:		Line 19:
	{{OptionalArg}}		{{OptionalArg}}
	{{New feature/item\|3.0150\|1.5\|\|		{{New feature/item\|3.0150\|1.5\|\|
	*'''compact:''' a [[boolean]] representing whether the string will contain whitespaces. To remove whitespaces from JSON ~~stirng~~, use ''true''. String will contain whitespaces per default.		*'''compact:''' a [[boolean]] representing whether the string will contain whitespaces. To remove whitespaces from JSON string, use ''true''. String will contain whitespaces per default.
	}}		}}