Special Character Normalization #1284
MatteoGisondi
started this conversation in
Feature request
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Description
Endpoints containing special characters are parsed such that they are treated as words when split.
OpenAPI Spec File
The problem can be seen in this (admittedly poorly written) API spec: https://geofeux.sopfeu.qc.ca/sopfeu-api/swagger/v1/swagger.json
Additional context
Currently generated client:
Desired:
Notably for example,
utilisateurs_r_é_serv_é_à_lusage_de_la_compagnie_lg2
should beutilisateurs_reserve_a_lusage_de_la_compagnie_lg2
, as it's quite illegible otherwise.Beta Was this translation helpful? Give feedback.
All reactions