The generated Service layer code contains Chinese characters

[Gkibify]

The generated Service layer code contains Chinese characters

[Gkibify]

I'm going to file this under clients and once they're released we can revisit. It looks like you're using the Fetch API client, you should be able to migrate as that will be the first one released.

I used the Axios client

[mrlubos]

Hey @Zixueban, what's the expected result?

[Gkibify]

Hey @Zixueban, what's the expected result?

I expect results to be entirely in English, not including Chinese. Why generate Chinese

[Gkibify]

This is the backend code @mrlubos

[mrlubos]

Service names are based on tags. Your tags don't have any English characters in them. So even if we stripped the Chinese characters, what would the expected result be?

[mrlubos]

The upcoming clients will do away with services altogether so you'll have one less thing to worry about though 🙌

[Gkibify]

Service names are based on tags. Your tags don't have any English characters in them. So even if we stripped the Chinese characters, what would the expected result be?

In the original openapi-typescript codegen repository, it will generate a Service, even if my tag is in Chinese

[Gkibify]

My tags should be kept in English, right? @mrlubos

[mrlubos]

You mean it would generate a service called literally Service? If so, that's because openapi-typescript-codegen doesn't support non-ASCII characters

[Gkibify]

You mean it would generate a service called literally Service? If so, that's because openapi-typescript-codegen doesn't support non-ASCII characters

Understood, there is no way to recognize Chinese labels as English, so that class names containing Chinese characters will not be generated

[mrlubos]

I'm going to file this under clients and once they're released we can revisit. It looks like you're using the Fetch API client, you should be able to migrate as that will be the first one released.