v0.9.0

Changelog:

* Dependencies were updated to toml 0.5.
* Sources were updated to use rust 2018
* A feature was added to read partial documents directly into a structure
  This feature was introduced as normal trait, but later a proc macro was added
  to easily derive it.

v0.8.0

Changelog:

* Switch error handling to `failure`.

v0.7.0

The "Yukon Release".

This release was made from Faro, Yukon, Canada. How awesome is that?

Here goes the changelog:

* API CHANGE: The `read`, `set`, `delete` and `insert` function took a
  `&String` before for the value path. This changed, they now want a `&str`.
  Existing Code _should_ work, as `String` derefs to `&str`.
* Dependencies "error-chain" and "regex" were updated (thanks Bruce Mitchener)
* Automatic de/serialization was added (See the new
  {read,insert,delete,set}_serialize functions)

I also learned that "mdbook" uses "toml-query" - I feel honored!

v0.6.0

From the changelog:

* `TomlValueReadTypeExt` requires now `TomlValueReadExt`.
* Changed API semantics for the typed read API: The functions return
  `Result<Option<_>>` again, not only `Result<_>`

v0.5.0

Release v0.5.0. Dependencies and minimum compiler version was updated,
one new feature introduced (typed reading).

Also have a look at the CHANGELOG file.

v0.4.0

This release bumps the error-chain dependency from 0.10 to 0.11. It is
not 0.3.2 because the exported error types are considered breaking API
change with the error-chain update.

v0.3.1

Bugfix release.

The patch for the bugfix which was fixed in this release can be found in
commit ebb4407, which should also be
considered the complete changelog here.

The release includes a new test case for an edge case of
`TomlValueInsertExt::insert()` functionality which was not tested before
and an appropriate fix for the bug discovered with this new test.

v0.3.0

This is a release that changes only the API (and adds some more tests,
but that's really a minor point).

We changed the interface of the read functionality in this release to
return `Result<Option<_>>` - so if you read from a toml document and the
value is just not there, you get an `Ok(None)`, instead of an error.

This change was made because forwarding the error was cumbersome.
Sometimes one just want to check whether a value is _there_ - without
this change a user had to check for the error kind and react
accordingly. With this new interface, we get the complete power of
pattern matching in this case.

Non-Breaking changes:

* Tests whether document entries get actually deleted in the delete
  routines.

v0.2.0

This release changes the interface of the library a bit, so we bump to
0.2.0 instead of 0.1.1!

Breaking changes:

* The interface for the CRUD functions take a &str instead of a &String
now
* The `insert*()` functions try to _create_ intermediate data structures
on the way while traversing the toml document. Consult the documentatoin
for more details and examples and also for what is _not_ working right
    now

Non-Breaking changes:

* Documentation for the logging macros (do not use in your code)
* A trait which combines the toml::Value extension traits into one
trait, which is also implemented on toml::Value

v0.1.0

I am finally publishing this crate.

This is the very first release of this crate and therefor contains
errors, I'm sure about that.

But the 120 tests work and I cannot think of more test right now.

So go ahead and test (hihihi) and if there are errors we will release
0.1.1 or 0.2.0 soonish...

And now celebrate!