Toni Müller

Hey @okuuva I'd now rebase this branch onto `main` and then create tag `v1.0.0` on the head of `main`. The two commits on this branch will then be on `main`....

I tried with this config ``` import { defineConfig } from '@hey-api/openapi-ts'; export default defineConfig({ base: '', // input: 'api.json', input: 'https://raw.githubusercontent.com/swagger-api/swagger-petstore/master/src/main/resources/openapi.yaml', output: 'src/app/core/api/__generated__', client: 'angular', types: { enums: 'typescript',...

Sure, I have the following in my `package.json` `scripts` section: ``` "generate-typescript": "openapi-ts" ``` And then I execute `npm run generate-typescript`

So first, you can try the petstore spec: https://raw.githubusercontent.com/swagger-api/swagger-petstore/master/src/main/resources/openapi.yaml , it also doesn't create enums anymore. And yes, I need enums. They represent the domain models I'm working with. I'll...

It's fine for me. But I wouldn't tag it as "Feature". As it worked before and is not working now, it's a regression bug but not a feature :) Thanks...

That's very helpful already, I think all needed enums are there now. What is interesting is that the casing changed in change to 0.42. There the enums where printed as...

PascalCase probably makes the most sense for now. But later we should go according to what's specified in #558

A nice addition would be to pull the `character` item out of the `status` icon completely. It doesn't belong in there, if the user want's to see both the `character`...

Good find! It indeed it supported by the fork.

I took some minutes and added a PR for this.