Philzen

Looks like this PR could also close https://github.com/OpenAPITools/openapi-generator/issues/9371

Any update on this?

@segunadebayo Kindly have a look. This reverts a breaking change in v2 that affected quite a lot of users, see linked issues for reference. Speaking for our team: we have...

@BANOnotIT why not simply `git revert 0f376650efce9eb2d2cba3484ffe4e3a73364504`? It comes down to the same thing w/o changing the Component's signature.

> It comes down to the same thing w/o changing the Component's signature. @BANOnotIT indeed i was wrong here. But with your proposed PR for me the problem still exists...

> One can't simply remove functionality in fix release. We're totally on the same page here, a breaking change in a minor version is unacceptable in a semver world. >...

> My personal opinion is to do a quick revert, then if the functionality is important enough, @ShawnFumo Yes, reverting that change would be most appreciated. Otherwise our current codebase...

> @Philzen any updates on this? this is a breaking change that was wrongly introduced and it's been hanging for a while... @augustoabreu i've now created #8462 which simply reverts...

Not sure if this is related, but i assume b/c there seems to be a missing link between actual version numbers and codenames. In my project i have an `.nvmrc`...

... of course, another option would be to remove `withXml` completely from the global options – which would lead to less code instead of more here, and at the end...