[Feature] support additional fields while parsing

[manchenkoff]

What is a problem? A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Related fields

• [ ] example
• [ ] examples
• [ ] style
• [ ] explode
• [ ] additionalProperties
• [ ] allowReserved
• [ ] encoding
• [ ] links
• [ ] callbacks

[sergei-maertens]

Note that the spec also supports extension in various places, which can have any key/value added into the schema, to further complicate things :grimacing:

[manchenkoff]

yep, thanks @sergei-maertens, I have a plan for that too 😄

[jacobm-splunk]

Hey @manchenkoff!

We've been evaluating a number of options for an OpenAPI parser and your library came up.

Unfortunately, we need support for custom extensions. I'm wondering if that is on the roadmap?

We could also dedicate some engineering time to contribute that feature, but I wanted to run it by you first since you said you had a plan for it.

Thanks

[manchenkoff]

Hey @jacobm-splunk, this feature is definitely on the roadmap, but unfortunately, I don't have enough time to work on it this year. I assume that I will be able to finish it not before February 2023. So, if you can contribute to that, highly welcome! 👍