All Versions
20
Latest Version
Avg Release Cycle
166 days
Latest Release
242 days ago

Changelog History
Page 2

  • v3.1.4 Changes

    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 Changes

    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 Changes

    April 08, 2018

    🛠 What was fixed?

    🛠 Fixed bug introduced in v3.1.1 with array indexes

  • v3.1.1 Changes

    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 Changes

    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 Changes

    September 11, 2017

    🛠 What was fixed?

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

  • v3.0.0 Changes

    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 👍

  • v2.3.0 Changes

    February 16, 2017

    What was added?

    ➕ Added a new function to both the Decoder and Encoder called RegisterTagNameFunc.

    NOTES:

    0️⃣ Once a custom function has been registered the default, or custom set, tag name is ignored and relies 100% on the function for the field name data.

    The return value WILL BE CACHED and so return value must be CONSISTENT.

  • v2.2.2 Changes

    February 15, 2017

    🛠 What was fixed?

    • 📜 Parsing of struct tag, by name, corrected for when multiple tags exists, this was corrected in #15 thanks @htmd

    P.S. in the future, I will change this so that instead of specifying the tag name, a function will be specified allowing for greater flexibility; but it would be a breaking change so leaving for now until needed.

  • v2.2.1 Changes

    February 13, 2017

    🛠 What was fixed?

    • ➕ Added additional notes to RegisterCustomTypeFunc to indicate that if a struct type is registered a url.Value must exist explicitly for the struct and not just the fields.

    eg. url.Values{"User":"Name%3Djoeybloggs"} will call the custom type function with User as the type, however url.Values{"User.Name":"joeybloggs"} will not.

    🛠 Fixes #14