gvsafronov/rapidjson
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
2,477 Commits 1 Branch 0 Tags
Commit Graph

756 Commits

Author SHA1 Message Date
Milo Yip
c511ce303f
Merge pull request #1250 from StilesCrisis/issue-1249-test 
Unit Test: Parsing "0e100" in full precision mode causes UB
 2018-06-18 23:54:53 +08:00
abolz
7101911d9b Run all the new tests in full-precision mode only 
until I know what the normal-precision algorithm really does...
 2018-06-16 15:23:44 +02:00
abolz
319944a11a Disable failing test for now 2018-06-16 14:55:07 +02:00
abolz
a757a2aeb8 Add more tests 
Some more need to be fixed.
 2018-06-16 14:31:48 +02:00
abolz
179277817d Add a test for BigInteger::operator<< 2018-06-16 13:48:33 +02:00
abolz
a0f9c5fc46 [Debug - clean up] 2018-06-16 12:32:17 +02:00
abolz
8b98f4a782 Workaround incorrect rounding in MSVC 2018-06-16 09:40:40 +02:00
abolz
292f787c04 [Debug] 2018-06-15 15:10:50 +02:00
abolz
a78c8e3a4f Add more tests (which need to be fixed) 2018-06-15 12:59:39 +02:00
abolz
7acbb87c2b Some more tests 2018-06-15 11:39:45 +02:00
abolz
4e9b4f6d6a Return 0 if binary exponent is too small 2018-06-15 11:32:32 +02:00
abolz
80dba56aca Add tests for issues with string-to-double conversions (#849, #1249, #1251, #1253, #1256, #1259) 2018-06-15 10:15:45 +02:00
bogaotory
6f7dcb30d9 again, in relation to solving issue #784, use SizeType-typed variable to indicate a none-zero length string has been given in the schema as default value for the json property; added an unittest Object_Required_PassWithDefault 2018-06-01 21:16:26 +01:00
Florin Malita
8269bc2bc2 Prevent int underflow when parsing exponents 
When parsing negative exponents, the current implementation takes
precautions for |exp| to not underflow int.

But that is not sufficient: later on [1], |exp + expFrac| is also
stored to an int - so we must ensure that the sum stays within int
representable values.

Update the exp clamping logic to take expFrac into account.

[1] https://github.com/Tencent/rapidjson/blob/master/include/rapidjson/reader.h#L1690
 2018-05-15 22:48:07 -04:00
John Stiles
1329cdecce Added test for issue #1251 2018-05-11 15:57:11 -07:00
John Stiles
cad3805737
Update readertest.cpp 2018-05-11 15:19:11 -07:00
John Stiles
f7d2cd2228 added test for parsing 0e100 2018-05-11 15:16:46 -07:00
Zoltan Kovago
0fdd8040ce fix compilation on windows with clang 2018-04-09 15:47:17 +02:00
Christian Semmler
9640209f78 remove superfluous typename 2018-03-26 13:29:52 +02:00
Christian Semmler
f8c8c32b42 fix C++03 compatibility 2018-03-26 13:16:31 +02:00
Christian Semmler
c8530d022f add test case for remote ref issue 2018-03-26 13:04:35 +02:00
MaximeBF
27424d5c09 Change long/ulong as int/uint on MSC unit tests to be more inline with other templated functions unit tests 2018-03-14 08:44:00 -04:00
MaximeBF
a37f9d1ecd Fix unsigned long as unsigned unit test 2018-03-08 07:33:26 -05:00
MaximeBF
a040fc3347 Add unittest for long as int in MSC platforms 2018-03-08 07:28:51 -05:00
luz.paz
915218878a Misc. typos 
Found via `codespell -q 3` in  downstream https://github.com/BlueBrain/Brayns
 2018-02-19 06:42:52 -05:00
Milo Yip
966987625c Add transcoding/validation to Writer::RawValue() 
Fix #1152
 2018-02-13 10:58:41 +08:00
Milo Yip
daabb88e00
Merge pull request #1068 from yurikhan/violationDetails 
Schema violation details
 2018-01-26 11:26:27 +08:00
Milo Yip
7641af690e
Merge pull request #1122 from svart-riddare/issue-1108 
Suggestion for issue #1108
 2018-01-26 10:59:11 +08:00
Milo Yip
b1e556d713
Merge branch 'master' into violationDetails 2018-01-13 22:34:58 +08:00
Milo Yip
03f5de9d7e
Merge pull request #1065 from yurikhan/invalidSchemaPointer 
Fix reported violated schema pointer when that schema is remote
 2018-01-13 21:17:56 +08:00
Milo Yip
d48290e387 Another try to fix travis build 2018-01-13 12:51:24 +08:00
Milo Yip
0d95d58f8b Try to fix travis build 2018-01-13 12:37:01 +08:00
Étienne Dupuis
44f2f9aa53 Added relevant unit tests for issue #1108 suggested improvement. 2017-11-27 10:38:01 +01:00
Yuri Khan
8c182e51e7 Flatten allOf keyword violations 2017-09-30 20:16:03 +07:00
KaitoHH
66541b8926 add unit test for cursorstreamwrapper 2017-09-29 17:24:07 +08:00
Yuri Khan
0566716802 Extend schema validation tests to compare error object 2017-09-24 12:56:55 +07:00
Yuri Khan
c2371584a0 Keep schema URI in GenericSchemaDocument and internal::Schema 2017-09-23 21:36:07 +07:00
Yuri Khan
379b337444 Add failing test for the case when a remote schema is violated (#1064) 2017-09-16 17:09:08 +07:00
Milo Yip
4a2f2729f1 Change from miloyip/rapidjson to Tencent/rapidjson 2017-09-13 17:03:23 +08:00
Christopher Warrington
e4c0ecf86b Guard against min/max macros in tests too 2017-09-05 18:27:02 -07:00
bluehero
c831675026 modify 2017-08-07 11:58:37 +08:00
bluehero
5fb06596a9 modify 2017-08-07 11:44:27 +08:00
bluehero
8ba1f84f47 modify unittest 2017-08-05 20:39:31 +08:00
bluehero
9eb7bf895c add unittest 2017-08-05 18:12:44 +08:00
Milo Yip
c34e3dfc72 Merge pull request #1018 from miloyip/issue1017_allOfHandler 
Fix #1017 allOf keyword fail with Writer handler
 2017-07-13 16:57:56 +08:00
Milo Yip
fcd2e1f60c Fix #1017 allOf keyword fail with Writer handler 
Gave up using static binding for null handler, because it cannot be
used with arbitrary handler type. Change `OutputHandler handler_` to
pointer type.
 2017-07-13 16:07:36 +08:00
Milo Yip
f624a3037c Merge pull request #1010 from pah/fixes/817-stringref-null 
Improve handling of NULL strings
 2017-07-10 10:08:21 +08:00
Philipp A. Hartmann
47c3c1ec9f Improved handling of NULL strings 
* Safely assert upon passing NULL string without length
   (requires usage of RAPIDJSON_ASSERT within an expression)
 * Allow using a NULL string together with an explicit length 0
   (GenericStringRef, GenericValue::SetString, ...), see #817
 * Add GenericValue::SetString(StringRefType, Allocator&) overload
 * Add tests for the various cases
 2017-07-09 14:46:59 +02:00
Philipp A. Hartmann
f1ba61c7ba unittest.h: change RAPIDJSON_ASSERT to allow usage in expressions 2017-07-09 14:31:29 +02:00
Philipp A. Hartmann
14218aeb0a ParseResult: improve bool conversion and add operator!= 
* Use safe-bool idiom for boolean conversion to avoid accidental
   misuse of ParseResult values (closes #989)
 * Add operator!= to support more comparison expressions
   (previously silently/erroneously used operator bool)
 2017-07-09 11:13:31 +02:00