Update parsing of nested container types for responses


- During work under another task I met a problem with compilation of
operations with deep nested responses.
For example, the array of arrays of strings, see below:

responses:
  '200':
     description: OK
     content:
       application/json:
         schema:
           type: array
           items:
             type: array
             items:
               type: string

The example above generates a QList<QList<QString>> list.
The list is parsed in the {{classname}}::{{nickname}}Callback() method.
We use the {{{returnBaseType}}}-key for parsing list's data.
But the {{{returnBaseType}}}-key returns `QList val` for nested arrays,
which leads to the compilation error.
The correct variant for our example would be `QList<QString> val`.

To solve the problem, instead of using the {{{returnBaseType}}}-key,
we should use direct fromJsonValue call:
::{{cppCommonNamespace}}::fromJsonValue(output, doc.array());

- add a similar solution for QMap<QMap<***>> variant:
::{{cppCommonNamespace}}::fromJsonValue(output, doc.object());

- add the submitDeepArray and the submitDeepMap operations to the
nested-structures.yaml file with a deep nested responses.
The expected test results are compilation succeed.

Note: 'uniqueItems' is a key word for OpenApi arrays. If it's true,
the generator generates QSet, otherwise QList. The reason is QSet
is more efficient in case of inserting unique items into big set
of data. But we don't need to handle the key {{#uniqueItems}} in the
edited block anymore, because for QSet the properly overloaded
fromJsonValue(QSet ... ) will be called anyway.

Pick-to: 6.12 6.11
Change-Id: Iff8a19e66aa4162a7477a71b51b25824a759e14f
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
commit0323c5571b9b0b5bda60a77c826eb02ce5e73129
parent835e51770b538083cc9c117b8de80bb7142dafd9
authorTatiana Borisova <tatiana.borisova@qt.io>
committerTatiana Borisova <tatiana.borisova@qt.io>
commit timeTue, 7 Jul 2026 15:35:08 +0000