Skip to content
This repository has been archived by the owner on Jul 19, 2020. It is now read-only.

Releases: yewstack/yew_router

v0.11.0

14 Mar 12:04
045fcbe
Compare
Choose a tag to compare
  • 🛠 Fixes

    • Fixed docs.rs document generation [254] (Thanks @jetli)
    • Fixed clippy for web_sys target [249] (Thanks @jetli)

v0.10.0

03 Mar 00:09
60fe08a
Compare
Choose a tag to compare
  • Bumped version of Yew from v0.12.0 to v0.13.0
  • This brings support for web_sys, which necessitates specifying either "web_sys" or "std_web" as a feature. (Thanks @tarkah)

v0.9.0

25 Feb 11:55
22c9978
Compare
Choose a tag to compare

0.9.0 2020-2-25

  • ⚡️ Features

  • 🛠 Fixes

    • Fix RouterAnchor href [228] @jetli
    • Undo non-passive state for prevent_default [240] @jetli

v0.8.1

10 Jan 13:18
f7dad13
Compare
Choose a tag to compare

0.8.1 (2020-1-10)

  • 🛠 Fixes

    • Fixed a dependency issue with wasm-bindgen that would cause builds to fail when building for the wasm32-unknown-unknown target.

v0.8.0

09 Jan 23:35
fbf88e3
Compare
Choose a tag to compare

0.8.0 (2020-1-9)

  • ⚡️ Features

    • Use a default type parameter of () to specify state-related type parameters instead of the old macro-based solution. [157]
    • Remove need for JsSerializable bound on the state parameter used for storing extra data in the history API.[185]
    • RouterLink and RouterButton now support having children Html. This deprecates the text prop. [192]
    • Fragment routing is now easily implementable by using an adapter because parser rules for the routing syntax were relaxed. [195] [211]
    • Support using this library only with the Switch derive, allowing it to run in non-web contexts. [199]
  • 🚨 Breaking changes

    • If you were using default-features = false, you will have to now specify features = ["service"] to get the same behavior as before. [199]
    • RouterAnchor and RouterButton now have props that take a route: SW where SW: Switch prop instead of a link: String and they now have a mandatory type parameter that specifies this SW. [207]
    • Route's state field now holds a T instead of an Option<T>. [205]
    • Using default type parameters to specify the state typ instead of the macro that generated a module (unit_state) means that any imports from that module should now be replaced with the path that the type normally has in the project. [157]
  • Inconsequential

    • Change state related type parameters from T to STATE. [208]

v0.7.0

11 Nov 17:31
4312f58
Compare
Choose a tag to compare

0.7.0 (2019-11-11)

  • ⚡️ Features

    • Greatly improve the quality of matcher string parsing errors. [171]
    • Bring back {}, {*}, and {<number>} capture syntax for tuple structs/enums variants.
      If your variant or struct doesn't have named fields, you don't need to supply names in the matcher string [116]
    • Redirects that happen in the Router component actually change the url in the browser [171]
    • Allow parsing (almost) any character after a # is encountered in matcher strings.
      This enables this library to be used as a fragment router. [150]
  • 🛠 Fixes

    • Allow ! to appear after {...} in matcher strings. [148]
    • Matcher strings can now start with &. [168]
  • 🚨 Breaking changes

    • Upgrade to Yew 0.10.0
    • Switch components now need to implement Clone in order to be used with the Router [171]

v0.6.1

01 Nov 17:25
9539905
Compare
Choose a tag to compare

Breaking Changes

  • None

Features

  • Allow a broader set of capture syntaxes for unnamed structs/variants. Identifiers don't need to be specified within the {} delimiters because the fields themselves don't have names. Now {}, {*}, and {3} are valid syntax when working with Tuple-structs/variants.
  • Allow ! special character in more places.
  • Rework parser "compiler" error messages. Better messages will be shown when there are errors in the routing syntax.
  • Add impl<SW: Switch, T> From<SW> for Route<T>. Now Routes can be created from Switches easily.
  • Allow escaping {, }, and ! special characters by using {{, }}, and !! respectively.
  • Provide a correct error message when attempting to derive switch for a Unit struct/variant with a capture group.

Bug Fixes

  • None

v0.6.0

24 Oct 19:46
8ae58b9
Compare
Choose a tag to compare

This release represents a significant departure from the prior works from both @saschagrunert and @hgzimmerman. So much so that it represents a new beginning for the project (real changelogs will be coming for subsequent releases).