Alexey Makhrov

@JoostK > Yes, this is an issue. We generate: > ```ts > "" + ((((null as any) ? (((ctx).prop /*24,28*/) /*24,28*/)!.nested : undefined) /*24,36*/).field /*37,42*/) /*24,42*/; > ``` > Is...

Oh I see! It would generate something like `(((ctx).a)?.b).c`, where the parens break the chain

It looks like the issue is much deeper than I imagined. Basically, the AST shape from the parser doesn't match the order of operations. Later the **compiler** reshapes this tree...

> This should be a non-breaking change since the effective types are the same If real enums are used (via the `stringEnums` option), it will be a breaking change, since...

I think targeting this for the 7.x branch is reasonable

One of the tests failed in CI. Looks to be what has just been fixed in this PR: https://github.com/OpenAPITools/openapi-generator/pull/13526 . Perhaps need to merge in latest changes from `master` here?

@macjohnny

Duplicate of https://github.com/OpenAPITools/openapi-generator/issues/10975

@paintcode Yes it has been fixed. This bug report effectively duplicates https://github.com/OpenAPITools/openapi-generator/issues/10975 and as such should have been closed together with that one. @wing328

Broken compilation was fixed in 6.0.0 (but still no body support in DELETE) Full support for body in DELETE landed in 6.2.0