-
Notifications
You must be signed in to change notification settings - Fork 278
fix/non seekable stream to v3 #2640
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
base: main
Are you sure you want to change the base?
Conversation
…ialization fix: additional properties serialization should not emit a schema in v2 fix: additional properties serialization should not emit booleans in v3.1+
…port/v2--components--Microsoft.OpenApi chore(support/v2): release 2.3.11
…o-v3 Signed-off-by: Vincent Biret <[email protected]>
| var initialPosition = stream.Position; | ||
| var firstByte = (char)stream.ReadByte(); | ||
|
|
||
| // Skip whitespace if present and read the next non-whitespace byte |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It feels like this comment is misleading. It mentions that it will read the next non-whitespace byte, but actually it seems like it reads the next byte unconditionally, regardless of what character it is. Considering whitespace is insignificant in JSON, it seems fair to assume multiple leading spaces are present. Changing the if to a while seems like it could do the trick?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the suggestion, it was a bit outside of the initial scope but I made the change.
Signed-off-by: Vincent Biret <[email protected]>
|



fixes #2638, reflection of #2639