Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

@respond-framework/rudy

respond-framework177MIT0.1.1-test.9

think of your app in states not routes (and, yes, while keeping the address bar in sync)

readme

changelog

Change Log

All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.

0.1.1-test.9 (2020-03-27)

Features

  • restore fallback for broken sessionStorage (#74) (8df1154)

0.1.1-test.8 (2019-12-20)

Note: Version bump only for package @respond-framework/rudy

0.1.1-test.7 (2019-11-13)

Features

BREAKING CHANGES

  • scroll restoration is enabled by default

Fixes https://github.com/respond-framework/rudy/issues/62

0.1.1-test.6 (2019-10-23)

Bug Fixes

  • rudy: export things used in tests (17bc948)

Code Refactoring

  • remove flow from builds (332e730)

BREAKING CHANGES

  • flow types are no longer available in published packages

0.1.1-test.5 (2019-10-16)

Bug Fixes

  • history: delete console.log from BrowserHistory (#58) (4d1a4e4), closes #46
  • history: store index of current history stack entry in the browser location state (#61) (3abd2b1)

BREAKING CHANGES

  • history: browsers that don't support the history API or session storage are no longer supported at all. In practice this means IE9 is no longer supported.
  • history: future entries in the history stack remain even if the user has since navigated from a previous entry to an external site (because they are no longer removed when they are potentially still the future entries in the browser stack)

Fixes https://github.com/respond-framework/rudy/issues/59

0.1.1-test.4 (2019-09-10)

Bug Fixes

  • history: pushing/replacing a route sometimes resulted in a back/next action (#56) (f6e06ad)

BREAKING CHANGES

  • history: dispatching a route that matches the previous/next route in the history stack is no longer reinterpreted as a back/next action
  • history: history functions set/setParams/setState/setQuery/setHash/setBasename no longer accept a function as an argument
  • history: history functions set/setParams/setState/setQuery no longer merge their arguments with the existing params/state/query
  • history: history functions back/next/jump no longer accept a state argument

Fixes https://github.com/respond-framework/rudy/issues/48

0.1.1-test.3 (2019-06-07)

Build System

  • add ability to publish to git instead of NPM (#34) (95e59e0)

Features

  • add compatibility with react-redux 6+ (#33) (cb45152)

BREAKING CHANGES

  • The object returned from createRouter now contains a key api which contains routes, ctx and such things. Previously they were in the root object.
  • The link package has been renamed to react.
  • The Link component now must be rendered as a descendant of the new RudyProvider.
  • The core no longer monkey patches redux getState to have a key api with the rudy API.
  • Remove UMD builds

0.1.1-test.2 (2019-06-06)

Bug Fixes

  • core: Pass the configured title state key or selector into the title middleware #28 (381d8c3)

0.1.1-test.1 (2019-04-15)

Features

  • add options to the call middleware (#17) (4ee0198)
  • transformations: Various changes, documentation (#24) (c7c2320)

BREAKING CHANGES

  • transformations: fromPath and toPath Have changed type signatures, and the defaults behave differently.

0.1.1-test.0 (2018-11-05)

Note: Version bump only for package @respond-framework/rudy