You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The swagger file generated with the library contains paths with regex, which make all the client tools to fail consuming the API.
For instance a url like this:
/test/{param1:regex1}/{param2:regex2}
is currently generating the following url in the swagger file:
/test/{param1:regex1}/{param2:regex2}
where it should instead generate:
/test/{param1}/{param2}
To solve this issue, I suggest using a regex like the following:
Theoretically transmute's path syntax isn't supposed to mirror any particular framework: it's a coincidence that it matches aiohttp. Of course I understand that doesn't really help you, just giving some background.
For a solution, how about we modify the transmute path syntax to allow arbitrary annotations after colons? basically, anything after the colon is framework-specific metadata. For aiohttp, this would actually make the path syntax identical to normal routes, so
/test/{param1:regex1}/{param2:regex2}
would just work.
Regarding running the tests: Sorry to hear uranium was difficult for you. Did you run into an issue with running
The swagger file generated with the library contains paths with regex, which make all the client tools to fail consuming the API.
For instance a url like this:
is currently generating the following url in the swagger file:
where it should instead generate:
To solve this issue, I suggest using a regex like the following:
that could be added right before https://github.com/toumorokoshi/transmute-core/blob/master/transmute_core/swagger/__init__.py#L59
I tried to do it myself, but can't figure out how this uranium stuff is working for testing, and don't really have time to invest in it :(
The text was updated successfully, but these errors were encountered: