Use extensions to name module functions and consolidate schema/operations into single files

[chazwatkins]

I've noticed some API specs, like Stripe, have extension attributes like x-stripe-method that should be used to name the function instead of the operation ID. Is there a configuration option to use extensions as the module function names?

Additionally, is there a configuration option to consolidate the Schemas and Operations into the same modules? For example, ' stripity_stripe' includes the schema and functions in the same module. Is this possible with the merge configuration option?

[aj-foster]

Great questions!

Is there a configuration option to use extensions as the module function names?

There is no configuration for this, but you can plug the naming logic to accomplish this. You can define your own processor:

config :oapi_generator,
  my_profile: [
    processor: MyLibrary.Processor
  ]

Inside MyLibrary.Processor, you can define operation_function_name/2 and use custom logic to determine the function name.

Additionally, is there a configuration option to consolidate the Schemas and Operations into the same modules?

If operations and schemas end up with the same module names, you should see them appear in the same module. Once the processor does the work of collecting and naming everything, the renderer just has to trusts that everything with the same name belongs together.