Swagger/OpenAPI 2.0 issue on additional properties

[benedictbasa]

When the addtionalProperties is used for specifying dynamic fields in the swagger 2.0 spec, it is encountering issue.

[jprobinson]

Howdy @benedictbasa. Without more information, I'm afraid I can't resolve this issue.

Would you mind please providing:

1. The error you encountered.
2. An example input that triggered this error.
3. An example of the output you expected for the .proto file afterwards.

Thanks!

[sukidesuaoi]

Hi @jprobinson, we are using object as type for the additionalProperties.

1. Error encountered:
   

2. Example of input:
   

[jprobinson]

Hi @sukidesuaoi, I'm afraid with this information, I'm unable to reproduce the error.

Can you please provide more context on your input schema, or at least an example schema that forces a similar error?

Also, I'm still unsure what you mean by "dynamic fields" in the issue description. Can you please include what you're expecting of the outputted Protobuf as well?

[sukidesuaoi]

Hi @jprobinson attaching here a sample of the json file. (Putting it as a txt file)
addProp.txt

The dynamic fields i'm referring to is supposedly like this:
map<string,google.protobuf.Any> Attributes = 31;

[melissop]

Hi @jprobinson ,
I get the same error while trying to generate a proto file using command below:
openapi2proto -spec TS29510_Nnrf_NFManagement-Swagger20.json > TS29510_Nnrf_NFManagement-Swagger20.proto

The error I get is
error: failed to transpile: failed to compile OpenAPI spec to Protocol buffers: failed to compile definitions: failed to compile #/definition/NfInstancesResponse: failed to compile properties for NfInstancesResponse: failed to compile property _links: failed to compile object property _links: failed to get type [object]: failed to find type object

additionalProperties type is object in my case also.

Attaching the input file with txt suffix.

TS29510_Nnrf_NFManagement-Swagger20.json.txt