[Improvement] Names should be nicer

[Zydnar]

This looks bad and it's not only about types.

If you work with huge government API it's hard to correct all names and there is no way to change operationId etc.

[jonkoops]

@Zydnar What is the name in the schema?

[Zydnar]

@jonkoops https://rejestr-bdo.mos.gov.pl/api/swagger/index.html here is json https://rejestr-bdo.mos.gov.pl/api/swagger/v1/swagger.json
same with: https://rejestr-bdo.mos.gov.pl/manufacturingreportapi/swagger/v1/swagger.json
and https://rejestr-bdo.mos.gov.pl/productreportapi/swagger/v1/swagger.json

Names are terribly long.

[fgnass]

@Zydnar I just had a look at the examples. I could imagine adding an option to remove package names from references, which would already help a lot. But there are also ref names which look super weird like this one:

#/components/schemas/WasteRegisterPublic.Api.ApiModels.Collections.PaginatedPage`1[[WasteRegisterPublic.Api.ApiModels.Responses.WasteRegister.WasteRecordCard.V1.KeoListItem, WasteRegisterPublic.Api, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]]

A possible approach could be to discard everything after the first non-world character and append a counter instead. So all the types that look like the one above would end up as PaginatedPage1, PaginatedPage2, etc.