github.com/smugmug/godynamo@v0.0.0-20151122084750-7913028f6623/CHANGELOG.txt (about)

     1  December 3, 2014
     2  ----------------
     3  
     4  - All endpoints now return []byte instead of string for the response body. This
     5    reduces some needless type transformations.
     6  
     7  
     8  October 27, 2014
     9  ----------------
    10  
    11  - Bring GoDynamo into conformance with substantial DynamoDB changes rolled out by
    12    AWS in October 2014.
    13  
    14  - This is a major, breaking change in the GoDynamo package. Caution is warranted,
    15    and users should expect existing code to require attention. Given the
    16    amount of code changed, bugs should be anticipated.
    17  
    18  - Types from the "endpoint" package are now broken out into their own
    19    files in the "types" directory.
    20  
    21  - In many cases, value types have been replaced by reference types.
    22  
    23  - Numerous other small inconsistencies, errors and issues have been addressed.
    24  
    25  - Tests have been updated to match new AWS examples.
    26  
    27  - Licensing has been removed from the top of each source file. The BSD license
    28    is now only a standalone file in the top directory of the repository.
    29  
    30  
    31  March 25, 2014
    32  --------------
    33  
    34  - Add keepalive support for programs that wish to use it. See README for sample use.
    35    Sample use launches a goroutine that HEADs your default DynamoDB url every five seconds.
    36    (bradclawsie)
    37  
    38  - Add support for changing the scheme and port of the DynamoDB url (see sample conf and
    39    README). (bradclawsie)
    40  
    41  - Add support for environment var conf file. (donholly)
    42  
    43  
    44  May 2015
    45  --------
    46  
    47  - Many users have requested parameterized configurations. It is clear that a global "conf.Vals"
    48    was not a useful solution for many people. This major update provides support for parameterized
    49    configurations at all levels of the api, and in all cases, this is the default. No apis have
    50    been broken - existing methods that assumed a global "conf.Vals" configuration variable will
    51    simply provide that as a parameter to the new functions, which have a naming scheme of
    52    "WithConf" (EndpointReq vs. EndpointReqWithConf etc). Your existing code should continue to
    53    work! If existing code breaks, please file an issue, my goal was to make this a transparent
    54    upgrade.
    55  
    56  - The "tests" directory now has live tests that use the parameterized configuration which you
    57    can use as examples to mine for code.