Good morning/afternoon/evening,
First of thanks a lot for maintaining this library and taking the time to read issues! Using libopenapi with the high level API makes working with OpenAPI v3.1 at least bearable.
While I was working on some code generation I did notice that it's currently not possible to add a description (or other fields) to a SchemaProxy created using CreateSchemaProxyRef which means that distinguishing among multiple values as described in JSON schema 7.7.1.1 is not possible.
Would maybe be-able to advice on how I could best add feature to libopenapi as I'm not that familiar with libopenapi inner workings, BC break policy and naming 🙈
Personally I was thinking about creating a CreateSchemaProxyWithRef which accepts a *Schema and ref string but the name is a bit confusing, another option would be to allow setting the rendered field using a setter on the SchemaProxy or maybe just add a schema argument to CreateSchemaProxyRef?
In any case thanks again and have a great day!
Cheers,
Warnar
Good morning/afternoon/evening,
First of thanks a lot for maintaining this library and taking the time to read issues! Using libopenapi with the high level API makes working with OpenAPI v3.1 at least bearable.
While I was working on some code generation I did notice that it's currently not possible to add a
description(or other fields) to aSchemaProxycreated using CreateSchemaProxyRef which means that distinguishing among multiple values as described in JSON schema 7.7.1.1 is not possible.Would maybe be-able to advice on how I could best add feature to libopenapi as I'm not that familiar with libopenapi inner workings, BC break policy and naming 🙈
Personally I was thinking about creating a
CreateSchemaProxyWithRefwhich accepts a*Schemaandref stringbut the name is a bit confusing, another option would be to allow setting therenderedfield using a setter on theSchemaProxyor maybe just add aschemaargument toCreateSchemaProxyRef?In any case thanks again and have a great day!
Cheers,
Warnar