Inline Serializer - RFC3986-compliant

[nathanmrtns]

Describe the bug
Using inline_serializer(name="Name with spaces"...) generates a component schema like Name with spaces:

components:
  schemas:
    Name with spaces:

Running the validate command, doesn't show any warnings about this, but if I paste the yml file into swagger editor, it complains about $ref values must be RFC3986-compliant percent-encoded URIs

A suggestion would be that the rfc compliant name wouldn't be required but we could show some warnings.
wdyt?

To Reproduce
Just use inline_serializer with name attribute with spaces.
Generate schema
Use the schema in swagger editor

Expected behavior
The editor show RFC Compliant errors

[tfranzel]

Running the validate command, doesn't show any warnings about this, but if I paste the yml file into swagger editor, it complains about $ref values must be RFC3986-compliant percent-encoded URIs

that is unexpected but entirely possible. The meta schema for OpenAPI on which the validation operates is not 100%.

Semantic error at components.schemas.Name with spaces
Component names can only contain the characters A-Z a-z 0-9 - . _

This must even be stricter than RFC3986. The issue with the ref is just a consequence of the invalid name. So quoting isn't an option either. We now emit a warning if names are bogus.

Good find! thx

[tfranzel]

closing this issue for now. feel free to comment if anything is missing or not working and we will follow-up.