Infer operation_id from function name

[slinkydeveloper]

Fix #4

[slinkydeveloper]

@Flowneee

[Flowneee]

I think generation of operationId should be an opt-in behavior, since it is not mandatory in specification. There 2 things needs to be done here IMO:

• parameter in Builder, which will enable generation of operationId from function names (.generate_operarion_id(bool)), which is false by default (which can be later changed in major releases)
• possibility to pass None (or empty string), which will not generate operationId property at all for current operation.

Also please describe changes in CHANGELOG

[slinkydeveloper]

@Flowneee how would you propagate a builder config option to the macro? I guess we could modify the signature of OperationGenerator into something like:

pub type OperationGenerator = fn(&mut Components, &BuilderOptions) -> Result<Operation, anyhow::Error>;

And then this BuilderOptions will take care of carrying the generate_operation_id_from_function_name field, which I can if-then within the generated code. WDYT?

[Flowneee]

@slinkydeveloper Yeah, I thought about something like that. We can then expand set of options, allowing to customize spec generation further. For now, since it is single parameter, I think BuilderOptions should be hidden inside OpenApiBuilder, and this option exposed as method of OptnApiBuilder::infer_operation_id.

But rename generate_operation_id_from_function_name to something shorter like infer_operation_id )