Poem/Openapi : Strategy for generating generic structure names about poem

[amtelekom]

#318 and #670 are about similar problems.
#671 implemented a solution for the generics problem, but sadly got no feedback so far.

The current output is non-compliant with the OpenAPI spec, even if SwaggerUI & Co don't complain:

All the fixed fields declared above are objects that MUST use keys that match the regular expression: ^[a-zA-Z0-9.-_]+$

(https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#components-object)

The problem I see with both your suggestion (Prefix with ListOf instead of wrapping in brackets) as well as the one in #671 (replace special characters with underscore) is that it might collide with non-generics that use the same name - but IMHO both solutions would be preferable to just not be able to use Generics at all without generating invalid OpenAPI specs.

@sunli829 would you be open to a PR that removes the disallowed characters, and if so, do you have a preference for the format (i.e., replace punctuation with underscores, Prefix with a String like "Of", ...)?

[sunli829]

Currently it is not possible to customize the OpenAPI name corresponding to a generic type. If you need a legal name, you can only avoid using generics.

[rxdiscovery]

I have a proposition,
why not take the template ( [{}] ) directly from a global variable, which can be modified?

  fn name() -> Cow<'static, str> {
        format!("[{}]", T::name()).into() 
    }

to

  fn name() -> Cow<'static, str> {
        format!(get_vec_gen_template(), T::name()).into() 
    }

[rxdiscovery]

Hello,

@amtelekom if we make the template dynamic so that each developer can customize it only for their needs

I think @sunli829 is so busy lately, it would be nice if he assigned a moderator to help him.