Is your feature request related to a problem? Please describe.
OpenAPI 3.0 does not natively support the full set of the JSON-Schema specification; notably, patternProperties and propertyNames are absent. Some tools instead use the x- prefix to support patternProperties and propertyNames in OpenAPI 3.0.
Describe the solution you'd like
Would it be possible for datamodel-code-generator to support x-patternProperties and x-propertyNames as well? It would be great as we currently have no way of upgrading to 3.1 soon, but we would still like to benefit from pattern properties and properly typed property names.
Describe alternatives you've considered
There is no real alternative; the model currently generated is just empty, which is kind of valid, as in it will ignore any patterned properties.
Additional context
A real-world snippet where we make use of both.
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too