Update dependency @vaadin/router to v1.5.2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
@vaadin/router (source)	dependencies	minor	1.4.2 -> 1.5.2

---

Release Notes

vaadin/vaadin-router

v1.5.2

Compare Source

Live Demo →
API Documentation →

Bug fixes

• e0da44a fix: change default baseUrl to be an absolute pathname (#​410)

  Fixes #​409. Previously, Vaadin Router taked base href as baseUrl which is later resolved against document.baseURI regardless it's a relative one or not. Semantically, baseUrl shouldn't be in relative form because it is the prefix of every route in the Router. With this change, it resolves the relative base href to be an absolute pathname before setting it as the baseUrl.

v1.5.1

Compare Source

Live Demo →
API Documentation →

Bug fixes

• 1bfd0ae fix: ensure location-changed event is timed after window.location update (#​407)

  Fixes #​340. Makes sure window.location is up-to-date when vaadin-router-location-changed.

• f2f9210 fix: add browser history states for non-initial redirects (#​406)

  Fixes #​324. Before the change, when Vaadin Router redirects, the new location was replacing the last browser history entry instead of adding a new one. With this change, only the initial Vaadin Router render, if redirects, replaces the last history entry, the second and subsequent renders always append history entries.

v1.5.0

Compare Source

Live Demo →
API Documentation →

New features

This release includes improvements on search query string and hash support (issue #​56).

• 63ee8d6 feat: support search and hash strings in Router.go (#​400)

  The Router.go navigation API method now accepts pathname with search and hash strings in a single in-app URL string:

  Router.go('/path?searchParam=value#footnotes');

  as well as separately:

  Router.go({pathname: '/path', search: '?searchParam=value', hash: '#footnotes'});

  The search and hash strings do not participate in route matching, however they are available in the action’s context argument and the component’s location property objects (see #​396).

• 9341511 docs: add demos for search and hash usage (#​397)

  This adds documentation on using search query string and hash string with Vaadin Router, including examples on how to access them from components and actions, and how to construct and parse search query strings using URLSearchParams native API.

Bug fixes

• b64acd8 fix: Router.go string pathname parsing in IE (#​401)

  Fixes a parsing bug concerning the search query string support in the URL API ponyfill Vaadin Router internally uses in browsers that lack native URL construction support.

• 5a37eb4 fix: ensure search and hash in context, location, and lifecycle (#​396)

  Makes search and hash strings consistently available in the Router API.

v1.4.3

Compare Source

Live Demo →
API Documentation →

Fixes

• store previousContext when reusing element (#​391)

• do not remove layout content that is not part of the route chain (#​392)

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

Newsflash: Renovate has joined WhiteSource, and is now free for all use. Learn more or view updated terms and privacy policies.