From e67e998736d220b13241fdbeb0eb7b19a4bedfeb Mon Sep 17 00:00:00 2001 From: balaskoa <Jeno.Balasko@ericsson.com> Date: Tue, 3 Dec 2019 11:50:35 +0100 Subject: [PATCH] typo only Signed-off-by: balaskoa <Jeno.Balasko@ericsson.com> Change-Id: I6ff68afdc55d8c344d3f5e15e57ec4686f018d96 --- usrguide/referenceguide/4-ttcn3_language_extensions.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/usrguide/referenceguide/4-ttcn3_language_extensions.adoc b/usrguide/referenceguide/4-ttcn3_language_extensions.adoc index 8c8a15564..c77016f15 100644 --- a/usrguide/referenceguide/4-ttcn3_language_extensions.adoc +++ b/usrguide/referenceguide/4-ttcn3_language_extensions.adoc @@ -5315,6 +5315,7 @@ This section covers the coding rules in general, the attributes controlling them === General rules and restrictions You can use the encoding rules defined in this section to encode and decode the following TTCN–3 types: + * anytype * array * bitstring @@ -5367,6 +5368,7 @@ Types imported from ASN.1 modules (from the list above) automatically have JSON When using <<legacy-codec-handling, legacy codec handling>> the encode attribute can be omitted if the type has at least one JSON variant attribute (see <<attributes-2, here>>). Additional requirements for JSON encoding and decoding when using legacy codec handling: + * in case of records, sets, unions and ASN.1 open types every field must also support JSON coding; * in case of array, record of and set of structures the element type must also support JSON coding. -- GitLab