-
Notifications
You must be signed in to change notification settings - Fork 128
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
Development/json number type #1382
Closed
Closed
Conversation
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
…f possible. In case the JSONRPC message reeived is malformatted, Thunder should try to return a JSONRPC error on malformatted JSON message in stead of: 1) Not responding at all. 2) Send an Web Error status even if the ID was sxtracted from the message. These fixes are related to: METROL-802/METROL-803
Starting or ending of an opaque structure should *only* contain white spaces. Anything else should be considered something to be parsed..
…earlier. In the mean time also prevented quoted areas from being accounted in the cope counting and in case we are deserializing in opaque areas drop the white space for further processing and storage.
…well.. Checking the validity of the JSONRPC messages coming in over the websockets. If incorrect, rturn an error if possible.
…heck the parameters for parsing errors.
…pedControlCharacters
Empty (opaque) strings should be quoted if enabled.
See issues: - METROL-779 - METROL 780 -METROL-781 - METROL-782 - METROL-795 - METROL-796 - METROL-797
Also remove unused code
Fall through from the previous case label is intentional.
…N parsing for NumberType<> Update 'test_jsonnumbertype.cpp' with matching test cases
msieben
force-pushed
the
development/JSONNumberType
branch
from
August 8, 2023 13:03
9edeef1
to
374a668
Compare
- Add quoted nullify support - Make serialization more robust
WARNING: A Blackduck scan failure has been waivedA prior failure has been upvoted
|
msieben
force-pushed
the
development/JSONNumberType
branch
from
August 17, 2023 13:14
8029942
to
44660f5
Compare
msieben
force-pushed
the
development/JSONNumberType
branch
from
August 17, 2023 14:12
44660f5
to
6c13b51
Compare
… a few warnings (#1395) * Adding pedantic warnings to Thunder, treating all warnings as errors, fixing some warnings from an older GCC version * Adding pedantic warnings to the project.cmake.in as well * Properly disabling one test that fails and needs to be fixed * Removing wpedantic werror from project.cmake.in to stop other modules from inheriting it
msieben
force-pushed
the
development/JSONNumberType
branch
from
September 4, 2023 14:49
951351b
to
1be7dc8
Compare
…by the more stringent build flags
…'development/JSONString'
msieben
force-pushed
the
development/JSONNumberType
branch
from
September 5, 2023 07:36
1be7dc8
to
9d83277
Compare
Superseded by #1433 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Amend 1381.