Is there a way to add a custom apiTemplateFile if queryParams are present? [dart-dio-next]

Description

I am trying to add an additional apiTemplateFile when some queryParams are present for the api.

For example, in the case of petstore.yaml, this is what I want to do:

lib
    - src
        - api
            - pet_api.dart
            - pet_api_query.dart      // <----- New file
            - store_api.dart
            - user_api.dart        
            - user_api_query.dart     // <----- New file
        - model
            - api_response.dart
            - category.dart
            - date.dart
            - order.dart
            - pet.dart
            - tag.dart
            - user.dart
        - api.dart
        - serailizers.dart
    openapi.dart

I intend to place some Built classes like this in the *_query.dart (ideally in a different folder than api), but only for operations that contain at least one query parameter.

abstract class FindPetsByStatusQuery implements Built<FindPetsByStatusQuery, FindPetsByStatusQueryBuilder> {

    FindPetsByStatusQuery._();

    factory FindPetsByStatusQuery([void Function(FindPetsByStatusQueryBuilder) updates]) = _$FindPetsByStatusQuery;

    String? get status;

}

What I have tried so far

• I have tried adding in a conditional statement inside the fromOperation method, but it still does not behave any differently. Am I looking/editing in the wrong place?
• I also have a feeling that I should create a supporting file. But again I could not find any documentation on how to create a supporting file for every operation that contains a queryParam.

Any help would be appreciated.

[kuhnroyal]

I see, but you won’t make it work with supporting files either. Those are meant to be used for single files like util classes etc. - you can not pass the operation. They always receive the full context.

You can try overriding generateApis, first call super, then filter out all operations with query parameters and basically repeat the block I linked above but only with the operations that you filtered.

[kuhnroyal]

You may be interested in the latest discussions here: https://github.com/OpenAPITools/openapi-generator/issues/6582 if you want to chip in there, you may be able to avoid having to roll your custom solution.

In the meantime, as you have noted, you have to add a supporting file somewhere in configureSerializationLibraryBuiltValue. Inside this template you iterate over {{#operations}} and figure out which one need which query generated. As I have noted in #6582 it may be useful to also generate extensions on the API classes that accept these query classes.