Initial setup questions; Interfaces, dates, PascalCase

[CorneThoes]

Hey everyone! Just started testing out this openapi generator. Does anyone know if its possible to, and if so how, to do my following questions:

• When using the date transformer, types get changed to have Date instead of string. However, a bunch of transformers are also generated that Are throwing an error because ( i think ) I dont use a client. Is it possible to not generate the transformers, but still have Date instead of string?

• Is it possible to swap from types to interfaces?

• I saw an open ticket that mentioned interfaces and PascalCase, is there a way to force the generated types to be PascalCase?

Thanks in advance!

[mrlubos]

Hi @CorneThoes! It sounds like your use case is to generate only types, am I correct? Can I ask why?

As for your questions, 1 and 2 are not current features. Are interfaces a mere preference or is there a reason for wanting them?

Your last question, can you provide an example of the transformation you'd expect?

[CorneThoes]

Hey @mrlubos! Thanks for the fast response!

Yes it is, we already have the entire cliënt setup. We have a generic crud service that uses factory functions to generate classes from the incoming interfaces/types. Furthermore, we use an interceptor that converts all json strings to dates, so using the transformer functions would actually be more code.

It's a shame we can't just do the date part, that means that the feature is currently bugged as no sdk/client + that transformer would create compiler errors. Is it possible to write our own transformer?
What I would expect the transformer to be able to do is set a date-time schema field to Date, without creating the function that says object.dateTimeField = new Date()

Interfaces are a preference because currently the features that types provide are not used, while we do use inheritance. Furthermore, it's easier for our junior devs to understand as we don't use the type features.

For PascalCase, I would expect any generated type to convert from snake, kebab or camel to be turned into Pascal I.e. equipment_types to EquipmentTypes. Some configuration to allow for diff
Erent usecases would be epic ( enums, properties etc.) Right now what I am doing is adding a ignore linter rule everyone I run the generator as the file does not adhere to the linter.

I'm asking all these questions because we want to stop manually creating the api models for now, and maybe the client in the future in nice understandable chunks.

I have researched about 7 generators over the weekend and this one looks the most promising quality wise, but is lacking a lot of configuration options. No way to generate a file per model, have not figured out how to write custom transformers yet. Interfaces, readonly properties, can't stop the schema file from generating(?) .

I would like to excuse my formatting, as I am sending this from my phone.

Thanks!

[CorneThoes]

Also, we are using the angular httpclient, and did not see a way to provide that as an input