All Versions
13
Latest Version
Avg Release Cycle
84 days
Latest Release
66 days ago

Changelog History
Page 1

  • v4.1.1

    November 17, 2019

    🛠 What was fixed?

    🛠 Fixed an out-of-bounds exception when a value exists but no parsable values.

  • v4.1.0

    November 11, 2019

    What's new?

    ⚡️ Updated deps that now use Go Modules.

  • v4.0.0

    October 18, 2019

    What's new?

    ⚡️ Updated to use Go Modules.

  • v3.1.4

    February 03, 2019

    🛠 What was fixed?

    🛠 Fixed an array/slice index issue for the custom decode function, thanks @vearutop for reporting the issue

  • v3.1.3

    April 10, 2018

    🛠 What was fixed?

    🛠 Fixed encoder issue when omitempty used in combination with a pointer. see #34 for details, thanks @mifanich for reporting

  • v3.1.2

    April 08, 2018

    🛠 What was fixed?

    🛠 Fixed bug introduced in v3.1.1 with array indexes

  • v3.1.1

    April 08, 2018

    🛠 What was fixed?

    in PR #32:

    • Corrected handling of array, not slice, values that can lead to
      a panic.
    • Rearranged logic to handle multiple values if index and non-index are
      mixed eg. Value=[]string{"1","2"} Value[2]=[]string{"3"}

    this resolves #29 and #30

  • v3.1.0

    February 04, 2018

    What 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.

  • v3.0.1

    September 11, 2017

    🛠 What was fixed?

    👀 empty boolean values are now set to false see here for details thanks @vearutop

  • v3.0.0

    July 31, 2017

    What'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 to AnonymousSeparate 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 👍