-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
_operationServers should be Maybe #17
Comments
Is there a problem with that behavior? |
The behavior becomes problematic when you try to parse openapi specifications from a file. (The (the exact same problem with #14) |
Or does the instance parse omitted fields as empty? In any case, an empty list and |
Decoder will set
This decisions re encoding/decoding exist already in |
Well, this is not a good thing. "An operation needs no authorization" ( The current behavior means that there is no way of setting "Inherit the authorization needed from the parent context" when encoding a spec, and when reading a spec "Inherit the authorization needed from the parent context" becomes "An operation needs no authorization". I don't think this is desired behavior.
Maybe I misunderstand something. Is the point of this package to match |
Is
No, I've just provided the historical context. Of course if those decisions happen to be wrong, they must be changed. I just didn't touch encoding code at all, hoping that it is OK. |
This package already serializes fields as missing. As far as I understand, in most cases a missing field and a field with I provided an excerpt from the OpenApi 3 spec in my initial comment. Are you suggesting that it is implying the omission of the field, instead of setting it to null? In either case, even if the correct behavior is to omit the field (I am now leaning towards that), the way to encode both a missing field, and |
servers
field description from the specification:This seems to indicate that the field should accept
null
values and be optional. This does not seem to be the case at the moment.I don't see how it would be possible to not override server objects.
The text was updated successfully, but these errors were encountered: