forked from virtuald/go-ordered-json
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix dotnet compatibility #11
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
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 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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,35 +1,18 @@ | ||
nspcc-dev fork of go-ordered-json | ||
=============== | ||
.NET-compatible JSON library | ||
============================ | ||
|
||
There are some legacy/stupid applications[1] that you need to interoperate with, | ||
and they for whatever reason require that the JSON you're using is ordered in | ||
a particular way (contrary to the JSON specifications). | ||
It's made for 100% compatibility with the JSON variation used by | ||
[Neo blockchain](https://github.com/neo-project/). There are three problems | ||
there: | ||
* it's ordered (that's why it's a fork of [go-ordered-json](https://github.com/virtuald/go-ordered-json)) | ||
* it has different conventions regarding control and "special" symbols | ||
* it has different conventions wrt incorrect UTF-8 | ||
|
||
Unfortunately, the golang authors are not willing to support such a broken use | ||
case, so on [their advice](https://groups.google.com/forum/#!topic/golang-dev/zBQwhm3VfvU) | ||
this is a fork of the golang encoding/json package, with the ordered JSON | ||
support originating with a patch from | ||
[Peter Waldschmidt](https://go-review.googlesource.com/c/7930/). | ||
The primary user of this library is [NeoGo](https://github.com/nspcc-dev/neo-go/), | ||
it has to be 100% compatible with C# implementation to correctly process | ||
transactions, that's why we're maintaining this library and solving any | ||
inconsistencies with .NET libraries if found. | ||
|
||
**If you can, you should avoid using this package**. However, if you can't | ||
avoid it, then you are welcome to. Provided under the MIT license, just like | ||
golang. | ||
|
||
Known broken applications | ||
------------------------- | ||
|
||
* [1][Windows Communication Foundation Json __type ordering](https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/stand-alone-json-serialization#type-hint-position-in-json-objects) | ||
* [2][NEO node](https://github.com/neo-project/neo/tree/master/src/neo/IO/Json) | ||
|
||
Fork motivations | ||
------------------------- | ||
|
||
NEO project has its own implementation of JSON serializer which is more a JSON | ||
dialect rather than standard-compatible implementation. Until JSON serialisation | ||
format affects contract states we need to be byte-to-byte compatible with the | ||
reference JSON serializer. This fork contains the following compatibility quirks: | ||
|
||
* JSON serializer is ordered (see https://github.com/nspcc-dev/neo-go/pull/2026) (implemented in the original [virtuald/go-ordered-json](https://github.com/virtuald/go-ordered-json) repository) | ||
* JSON serializer escapes non-ascii characters while marshalling (see https://github.com/nspcc-dev/neo-go/pull/2174) | ||
|
||
More compatibility quirks may be added in the future. |
This file contains 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 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 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 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 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 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.
👀