re
/
gjson
forked from mirror/gjson
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
120 Commits 1 Branch 60 Tags 610 KiB
Commit Graph

120 Commits

Author SHA1 Message Date
Josh Baker 080cd22816 fix mysterious missing result 
fixes #54
 2017-12-13 16:29:27 -07:00
Josh Baker 182ad76050 Array() from null becomes zero length Go array 
fixes #53
 2017-12-01 14:13:24 -07:00
Josh Baker 67e2a63ac7 Merge branch 'erikjohnston-fix-raw-false' 2017-11-20 11:50:05 -07:00
Erik Johnston 922b012d22 Fix bug where Result.Raw of literal 'false' was 'f' 2017-11-20 17:59:58 +00:00
Josh Baker ac7b6ae6f2 deprecated unmarshalling 2017-10-18 05:19:20 -07:00
Josh Baker 5a69e67cfd GetMany result value missing, fixes #48 2017-09-25 04:39:06 -07:00
Josh Baker 3c91814cf6 GetMany result incorrect, fixes #47 2017-09-25 04:37:57 -07:00
Josh Baker be96719f99 incomplete surrogate codepoints, fixes #38 2017-08-30 10:08:10 -07:00
Josh Baker 4e8f0c7f28 added playground link 2017-08-14 18:16:21 -07:00
Josh Baker ccc7f39b3a added IsObject IsArray helper functions 2017-08-14 08:23:21 -07:00
Josh Baker 6daf3373dc Moved benchmark code 
Moved benchmark to a different repository to avoid the fetching of
unneeded imports. Please find these benchmarks at
https://github.com/tidwall/gjson-benchmarks
 2017-08-14 08:21:16 -07:00
Josh Baker c784c41781 Allow parsing of large integers 
This commit fixes an issue in which GJSON was not representing integers
correctly that were greater than 53-bits when calling the result.Int()
and result.Uint() functions. This happened because GJSON stored all
numbers as float64s in the result.Num field, and Int()/Uint() would
simply try to convert the float64 to int64/uint64 by issuing
int64(result.Num) or uint64(result.Num) operations.

Now rather than a simple cast, GJSON checks to see if the float64 is a
whole integer and if the integer can fit within 53-bits. If so, then
the cast method can be used. Otherwise GJSON attempts to parse the
result.Raw directly. If that fails too, it falls back to the original
method.

This fix should maintain compatibility with existing applications.

thanks @joelpresence for reporting
fixes #29
 2017-05-25 19:39:18 -07:00
Josh Baker 0623bd8fbd Merge pull request #27 from kshvmdn/master 
Minor README clean-up
 2017-05-10 20:52:25 -07:00
Kashav Madan 8eb5c54ee3 Minor README clean-up 2017-05-10 23:42:56 -04:00
Josh Baker 617caec145 Update README.md 2017-05-08 21:47:28 -07:00
Josh Baker 2e78916f4a option to disable validation 2017-05-08 17:47:46 -07:00
Josh Baker 2555fc0b61 Unmarshal Validation 
The Unmarshal function now returns an error if the JSON is not valid.
 2017-05-08 17:33:03 -07:00
Josh Baker 0bedaf01cb updated wording 2017-05-08 07:47:07 -07:00
Josh Baker 371acf8f0c updated wording 2017-05-08 07:40:56 -07:00
Josh Baker 19194a58d8 typos 2017-05-08 06:55:29 -07:00
Josh Baker 3f5adf1ba9 New gjson.Unmarshal function 
It's a drop in replacement for json.Unmarshal and you can typically see
a 3 to 4 times boost in performance without the need for external tools
or generators.

This function works almost identically to json.Unmarshal except that
it expects the json to be well-formed prior to being called. Invalid
json will not panic, but it may return back unexpected results.
Therefore the return value of this function will always be nil.

Another difference is that gjson.Unmarshal will automatically attempt
to convert JSON values to any Go type. For example, the JSON string
"100" or the JSON number 100 can be equally assigned to Go string,
int, byte, uint64, etc. This rule applies to all types.
 2017-05-07 18:26:54 -07:00
Josh Baker e30a9c1037 Default String() to empty when nonexistent or null 
This commit alters the behavior of string handling.

Prior to this change, calling result.String() for nonexistent and null
JSON members would return "null". This runs counter to the zero and omitempty
defaults of Go. Thus I've been seeing in the wild:

    s := result.String()
    if s == "null" || s == "" {
        // ... handle empty string condition
    }

Now we can simply write:

    if result.String() == "" {
        // ... handle empty string condition
    }

It's still possible to explicitly check for null and existence.

    result.Type == gjson.Null
    result.Exists()
 2017-04-18 09:28:51 -07:00
Josh Baker 039b641eab added result.Time() function 2017-04-14 17:58:25 -07:00
Josh Baker 6e0babc7e8 updated benchmarks, added features list 2017-04-14 11:13:32 -07:00
Josh Baker a8ccb8767a mention "values" 2017-04-12 14:16:56 -07:00
Josh Baker 7d884e04ac minor update 2017-04-12 14:14:42 -07:00
Josh Baker 7c63fbd56a better test coverage 2017-04-11 08:54:19 -07:00
Josh Baker 92a0497357 reduced some complexity 2017-04-10 20:45:34 -07:00
Josh Baker 766ad13f76 minor updates 2017-04-10 12:26:09 -07:00
Josh Baker 9c689b0be6 cleanup benchmarks 2017-04-10 11:41:37 -07:00
Josh Baker 635226ae42 minor format updates 2017-04-10 11:41:19 -07:00
Josh Baker 20d521de6e added emoji test 2017-04-09 19:40:55 -07:00
Josh Baker 01736e2faf inlined unicode decoding 2017-04-05 10:22:45 -07:00
Josh Baker 458c2c85b8 reorg imports 2017-04-04 10:46:00 -07:00
Josh Baker e0cd4f26a8 proper emoji decoding, fixed #23 2017-04-04 10:42:36 -07:00
Josh Baker 8f291465f6 added Exists() to the list of handy functions 2017-04-02 10:13:06 -07:00
Josh Baker e8d1a9ab93 end of path regression, fixes #21 
thanks @Poorva17
 2017-03-29 08:19:50 -07:00
Josh Baker 9944282cf6 updated comments 2017-03-29 08:18:26 -07:00
Josh Baker 256887a8aa Fix for invalid matching on prefixed key 
Thanks to @Poorva17 for finding this issue.
Fixes #20
 2017-03-28 17:04:10 -07:00
Josh Baker 09d1c5c5bc added gjson-safe comment 2017-02-05 09:10:42 -07:00
Josh Baker e3f249f4fd Missing package alias 2016-12-16 09:22:41 -07:00
Josh Baker b0e589ad0b index for iterator vals 2016-12-08 15:00:05 -07:00
Josh Baker 456225d161 key index for ForEach 2016-12-07 16:37:33 -07:00
Josh Baker c1e65a498d added ParseBytes 2016-12-02 11:59:39 -07:00
Josh Baker 1a8de7c426 add query operators 2016-12-02 11:53:14 -07:00
Josh Baker 7afd24f7a2 added != comparison operator 2016-11-30 14:38:08 -07:00
Josh Baker 90669a0cbe query matching with % 2016-11-30 14:32:17 -07:00
Josh Baker 6fd75099ef Update README.md 2016-11-30 12:04:48 -07:00
Josh Baker 62892351c5 added ForEach function 2016-11-30 10:50:59 -07:00
Josh Baker 86b1b630e4 Query array for multiple matches 
It's now possible to query an array for multiple matches by adding the
'#' character immediately following the query.

For example, using the following JSON:

  {
    "friends": [
      {"first": "Dale", "last": "Murphy"},
      {"first": "Roger", "last": "Craig"},
      {"first": "Jane", "last": "Murphy"}
    ]
  }

To return the first match:

  `friends.#[last="Murphy"].first` >> "Dale"

To return all matches:

  `friends.#[last="Murphy"]#.first` >> ["Dale","Jane"]

Thanks to @chuttam for requesting this feature, closes #15.
 2016-11-30 07:59:24 -07:00