-
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
Open
baywet
wants to merge
10
commits into
main
Choose a base branch
from
fix/non-seekable-stream-to-v3
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
275dd9d
Merge pull request #2630 from microsoft/fix/additional-properties-ser…
baywet 6115e5f
chore(support/v2): release 2.3.11
release-please-token-provider[bot] 1f9bff4
Merge pull request #2632 from microsoft/release-please--branches--sup…
baywet 2436d73
fix: non-seekable json streams would fail to load as a document
baywet ca388ff
Merge branch 'fix/non-seekable-stream' into fix/non-seekable-stream-t…
baywet f9e5248
fix: reading streams in an asp.net context would cause async exceptions
baywet 770047f
Merge branch 'fix/non-seekable-stream' into fix/non-seekable-stream-t…
baywet fff8759
chore: linting
baywet 9cf530c
Merge branch 'fix/non-seekable-stream' into fix/non-seekable-stream-t…
baywet 6461bac
fix: load JSON documents that are preceded by multiple whitespace
baywet File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
ifto awhileseems 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.