The hierarchical, parent-child relationships between response_param_name and body_param_name resources are not being preserved, and the Type values in the response schema do not appear. Instead, all resources are enumerated in one long list and traversable responses are not expandable.
Example Response Schema:
The types for each of the above response_param_name resources from top to bottom should be String, Integer, Array, and Hash.
The parent-child relationship should look like this:
Both DeveloperProducts and DeveloperproductsElement are traversable and should be expandable in the UI to reflect this.
This issue is likely related to the <component_name>_id (i.e. the id of the parent resource) not being sent in create requests. Changes to SchemaBuilder may be necessary so that the correct parent id values are included in built schemas and accessible by the endpoints_import_service.
The hierarchical, parent-child relationships between
response_param_nameandbody_param_nameresources are not being preserved, and theTypevalues in the response schema do not appear. Instead, all resources are enumerated in one long list and traversable responses are not expandable.Example Response Schema:
The types for each of the above
response_param_nameresources from top to bottom should beString,Integer,Array, andHash.The parent-child relationship should look like this:
Both
DeveloperProductsandDeveloperproductsElementare traversable and should be expandable in the UI to reflect this.This issue is likely related to the
<component_name>_id(i.e. the id of the parent resource) not being sent in create requests. Changes toSchemaBuildermay be necessary so that the correct parent id values are included in built schemas and accessible by theendpoints_import_service.