Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): bump vue-router from 4.0.12 to 4.1.5 #9

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Sep 5, 2022

Bumps vue-router from 4.0.12 to 4.1.5.

Release notes

Sourced from vue-router's releases.

v4.1.5

Please refer to CHANGELOG.md for details.

v4.1.4

Please refer to CHANGELOG.md for details.

v4.1.3

Please refer to CHANGELOG.md for details.

v4.1.2

Please refer to CHANGELOG.md for details.

v4.1.1

Please refer to CHANGELOG.md for details.

v4.1.0

Vue Router 4.1

We are excited to announce the release of Vue Router 4.1 with a few new interesting features, better support for Node ESM and no breaking changes.

Omitting the component/components option in routes

It's now possible to completely omit the component option when defining routes with children. While nested routes are about defining layouts, they are also directly connected to a path and users often found themselves defining a pass through component that would just render a <RouterView> component to reuse the path structure. You can now simplify this to:

- import { RouterView } from 'vue-router'
- import { h } from 'vue'
-
 const routes = [
   {
     path: '/admin',
-     component: () => h(RouterView),
     children: [
       { path: 'users', component: AdminUserList },
       { path: 'users/:id', component: AdminUserDetails },
     ],
   },
 ]

In other words, you can now nest paths without having to define a component.

Passing History State in navigations

Passing History State through router.push() has been implemented and used by the router since its version 4.0 but hasn't been exposed as a public API until now. This enables passing a state property when calling router.push() or router.replace(). This is useful to pass global state to be associated with the history entry that cannot be shared by copying the URL. One common example of this are Modals:

// go to /users/24 but show a modal instead
router.push({ name: 'UserDetail', params: { id: 24 } state: { backgroundView: ... } })

... (truncated)

Commits
  • fce0fc1 release: vue-router@4.1.5
  • fdbaf83 feat(warn): warn against removed params
  • d56ba0a chore: wording in changelog [skip ci]
  • 3debfe8 chore: alternative in changelog [skip ci]
  • 4cc3093 feat(warn): better wording
  • 9f89b11 release: vue-router@4.1.4
  • 5b8983d fix(build): remove devtools in cjs production
  • b1cd7eb chore: note
  • 57a2b34 Docs: Add VF2 banner (#1520)
  • add447b feat: pass state in guards and redirect
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Sep 5, 2022

Dependabot tried to add @lowlighter as a reviewer to this PR, but received the following error from GitHub:

POST https://api.github.com/repos/bagussatoto/Evoting-Client-AMIKOM/pulls/9/requested_reviewers: 422 - Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the bagussatoto/Evoting-Client-AMIKOM repository. // See: https://docs.github.com/rest/reference/pulls#request-reviewers-for-a-pull-request

@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Sep 5, 2022

The following labels could not be found: 📦 dependencies.

@vercel
Copy link

vercel bot commented Sep 5, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
evoting-client ✅ Ready (Inspect) Visit Preview Oct 22, 2022 at 11:45AM (UTC)

Bumps [vue-router](https://github.com/vuejs/router) from 4.0.12 to 4.1.5.
- [Release notes](https://github.com/vuejs/router/releases)
- [Commits](vuejs/router@v4.0.12...v4.1.5)

---
updated-dependencies:
- dependency-name: vue-router
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Oct 24, 2022

Superseded by #13.

@dependabot dependabot bot closed this Oct 24, 2022
@dependabot dependabot bot deleted the dependabot-npm_and_yarn-vue-router-4.1.5 branch October 24, 2022 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants