Release (0.6.0) tracking issue.

[hgzimmerman]

• Allow components to accept children elements yew#589 needs to be merged.

• Component orphaning should be addressed Components use case with WARN msg yew#604

• Route syntax needs to be finished and thoroughly tested Add optional sections #38

• Doc-comment all public facing items.

• Yew 0.9 needs to be released (w/children and orphaning fixes)

• Rename project to avoid colliding with yew-router crate

• Integrate existing yew-router, and implement a fully working version of Ideas for the future API saschagrunert/yew-router#1

[hgzimmerman]

Orphaning being addressed isn't required, but If it isn't this lib can be released without too much trouble, Just tell people to not nest components.
Route syntax might be able to be relaxed in a few places, but is otherwise done.
I need to forbid undocumented public items.

[saschagrunert]

Feel free to simply push over https://crates.io/crates/yew-router, but I guess it needs to be a higher version. What do you think about 1.0.0? :)

[hgzimmerman]

I feel like a 1.0.0 would be a little much of a commitment at the moment - ie committing to no breaking changes (at least on a short timescale). I want to get a couple of releases in to iron out bugs considering how much just changed.

But you are right, we are now targeting 0.6.0 as a minimum.

[hgzimmerman]

Ok, I think its getting time to cut a release.

The following issues should be resolved before the release is made:
#105
#104
#121

UUID and date support can come later, as well as no/unnamed matchers for unit/tuple structs and enums. Those represent smaller breaking changes that won't break anyone's Switch derive.

The plan should be to release 0.6.0 nowish, then have master track yew's master branch, and cut a 0.7.0 release when yew 0.10.0 is released. People are forking this project to keep up with yew's master branch, and I would rather they didn't have to go to that effort.