Changelog History
Page 1
-
v4.1.1 Changes
November 17, 2019๐ What was fixed?
๐ Fixed an
out-of-bounds
exception when a value exists but no parsable values. -
v4.1.0 Changes
November 11, 2019What's new?
โก๏ธ Updated deps that now use Go Modules.
-
v4.0.0 Changes
October 18, 2019What's new?
โก๏ธ Updated to use Go Modules.
-
v3.1.4 Changes
February 03, 2019 -
v3.1.3 Changes
April 10, 2018 -
v3.1.2 Changes
April 08, 2018๐ What was fixed?
๐ Fixed bug introduced in v3.1.1 with array indexes
-
v3.1.1 Changes
April 08, 2018 -
v3.1.0 Changes
February 04, 2018What was added
- โ Added setting for string form value into
interface{}
values; previously they were ignored. thanks @Xzya for the issue
Why only string and not int, float etc...?
Because theres no way to tell what type the value should be; just because it CAN be parsed into an int, doesn't mean it should be for your application and so I have left it at setting strings. - โ Added setting for string form value into
-
v3.0.1 Changes
September 11, 2017 -
v3.0.0 Changes
July 31, 2017What's new?
- โ Added Embedded struct support
- โ Added
omitempty
just like std lib JSON
Made a version bump to v3.0.0 because the new Embedded struct logic has the potential to affect existing clients.
0๏ธโฃ The Encoder has a new option
SetAnonymousMode(...)
by default it embeds anonymous struct info as if the fields were part of the containing struct itself; to continue to have it split out the Embedded structs just set mode toAnonymousSeparate
and it will function exactly as previous versions.๐ please see examples detailing new functionality.
NOTE: if a struct and embedded struct have the same field, this will decode the value into both fields as there is no way to tell which you want; decoding into only the Embedded struct is still supported, again see examples.
๐ฑ Thanks to @danielchatfield and @michael2m for creating issues to get these features on the radar ๐