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
I'm not sure if this is a swagger bug, the documentation, or the api itself, but I wanted to make note of it.
I suspect that swagger may be putting some literal strings in place of what should be null/empty values.
Expected Behavior
I'd expect to be able to leave optional fields empty in the swagger forms.
Current Behavior
If I leave from_version empty in the swagger form, I get 4xx responses back. Note that this field has the following legend
ID of the “before” Version. If omitted, it will be treated as the version immediately prior to to_version.
and isn't marked as required.
Steps to Reproduce (for bugs)
leaving from version blank, leads to a request like this:
I was using swagger to try to validate a bug fix just using the tooling that was already here.
Your Environment
The text was updated successfully, but these errors were encountered:
jsnshrmn
changed the title
Swagger forms on home page leaves stuff in place of empty optional fields
Swagger form on home page doesn't let me create annotations with blank from_version
Dec 5, 2018
Yeah, this is partially a Swagger bug and partially the fact that having {thing}..{other_thing} in the path is invalid (at least in Swagger v2, and we haven't updated to v3, a.k.a OpenAPI).
Some folks have suggested that we change that to {change_id} and then set out in the description that {change_id} = '{from_id}..{to_id}'. ¯\_(ツ)_/¯
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.
I'm not sure if this is a swagger bug, the documentation, or the api itself, but I wanted to make note of it.
I suspect that swagger may be putting some literal strings in place of what should be null/empty values.
Expected Behavior
I'd expect to be able to leave optional fields empty in the swagger forms.
Current Behavior
If I leave
from_version
empty in the swagger form, I get 4xx responses back. Note that this field has the following legendSteps to Reproduce (for bugs)
leaving from version blank, leads to a request like this:
or
and gets me varying 4xx responses
filling it in shows a request like this:
and succeeds
Context
I was using swagger to try to validate a bug fix just using the tooling that was already here.
Your Environment
The text was updated successfully, but these errors were encountered: