Uh oh!
There was an error while loading. Please reload this page.
Fixed format of 'base64' to correct 'byte' - #2192
Conversation
I'm not sure this is right [EDIT: it is right], and in any event for 3.1 we should be directing people away from I'm not sure if we have an issue tracking that, if not I'll file one today. |
hkosova
commented
Apr 4, 2020
handrews
commented
Apr 4, 2020
@hkosova that's at least related. I didn't manage to file an issue but I discovered a 2/3rds done PR in my local repo. Wonder when I did that... I'll try to post that soonish. |
handrews
commented
Apr 5, 2020
@smhc all of this stuff is in the middle of being changed around for OAS 3.1, that's why it doesn't make any sense right now. |
handrews
commented
Apr 5, 2020
Let me finish updating this section with my PR that aligns it with previous work done to update OAS 3.1 to use the latest JSON Schema. If it still doesn't make sense, let's work through it then. |
handrews
commented
May 27, 2020
This is being addressed as part of PR #2200, which drops If there will be an OAS 3.0.4, then a decision on |
No description provided.