cloud-py-api / cloud_py_api

Nextcloud framework for developing apps using Python
https://apps.nextcloud.com/apps/cloud_py_api
GNU Affero General Public License v3.0
51 stars 7 forks source link

fix(deps): update dependency vue-router to v4 #24

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vue-router ^3.5.3 -> ^4.0.0 age adoption passing confidence

Release Notes

vuejs/router ### [`v4.1.6`](https://togithub.com/vuejs/router/releases/tag/v4.1.6) [Compare Source](https://togithub.com/vuejs/router/compare/v4.1.5...v4.1.6) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/router/blob/main/packages/router/CHANGELOG.md) for details. ### [`v4.1.5`](https://togithub.com/vuejs/router/releases/tag/v4.1.5) [Compare Source](https://togithub.com/vuejs/router/compare/v4.1.4...v4.1.5) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/router/blob/main/packages/router/CHANGELOG.md) for details. ### [`v4.1.4`](https://togithub.com/vuejs/router/releases/tag/v4.1.4) [Compare Source](https://togithub.com/vuejs/router/compare/v4.1.3...v4.1.4) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/router/blob/main/packages/router/CHANGELOG.md) for details. ### [`v4.1.3`](https://togithub.com/vuejs/router/releases/tag/v4.1.3) [Compare Source](https://togithub.com/vuejs/router/compare/v4.1.2...v4.1.3) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/router/blob/main/packages/router/CHANGELOG.md) for details. ### [`v4.1.2`](https://togithub.com/vuejs/router/releases/tag/v4.1.2) [Compare Source](https://togithub.com/vuejs/router/compare/v4.1.1...v4.1.2) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/router/blob/main/packages/router/CHANGELOG.md) for details. ### [`v4.1.1`](https://togithub.com/vuejs/router/releases/tag/v4.1.1) [Compare Source](https://togithub.com/vuejs/router/compare/v4.1.0...v4.1.1) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/router/blob/main/packages/router/CHANGELOG.md) for details. ### [`v4.1.0`](https://togithub.com/vuejs/router/releases/tag/v4.1.0) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.16...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 `` component to reuse the `path` structure. You can now simplify this to: ```diff - 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](https://developer.mozilla.org/en-US/docs/Web/API/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: ```js // go to /users/24 but show a modal instead router.push({ name: 'UserDetail', params: { id: 24 } state: { backgroundView: ... } }) ``` To see a full example, [check the modal e2e test](https://togithub.com/vuejs/router/blob/main/packages/router/e2e/modal/index.ts), it has been updated to use the `state` property. It's worth noting this **shouldn't be used to pass fetched data or complex objects such as classes** because of type and size limitations. [Check the History State documentation](https://developer.mozilla.org/en-US/docs/Web/API/History/state) for more information about the `state` property. Given the nature of the ``'s `route` prop, there is also a new function `loadRouteLocation()` that can be used on a *resolved route location* to load a route with lazy loading: ```js import { loadRouteLocation } from 'vue-router' const loadedRoute = await loadRouteLocation(router.resolve('/users/24')) ``` #### Typed Routes ![RouterLink to autocomplete](https://user-images.githubusercontent.com/664177/176442066-c4e7fa31-4f06-4690-a49f-ed0fd880dfca.png) In v4.1 we were initially planning to introduce types to automatically detect the params from a `path` property, creating autocomplete and type safety in `router.push()` and ``'s `to` prop. It was implemented but also turned out to be **extremely slow** after ~50 routes due to the nature of the types relying on nesting and complex unions. **Instead, we are introducing a build plugin** to generate the types of the routes for you based your **file structure**. This is similar to [Nuxt](https://nuxtjs.org/) and [Vite Plugin Pages](https://togithub.com/hannoeru/vite-plugin-pages) but with full type support (similar to [nuxt-typed-router](https://togithub.com/victorgarciaesgi/nuxt-typed-router)) **while allowing you to keep using the exact same API**, just with Autocompletion and typing hints 😄. The plugin currently supports Vite, Webpack (with some caveats), and rollup and **it's currently experimental** to gather feedback from the community and build a flexible solution. We hope to release a stable version in the following months. [Check out the plugin](https://togithub.com/posva/unplugin-vue-router) GitHub repository for installation instructions and documentation. Here are some other examples of how much this plugin can improves your developer experience: |![params validation in RouterLink](https://user-images.githubusercontent.com/664177/176442076-553811df-6190-472c-a958-914bbd6783db.png)|![Route infer from if condition](https://user-images.githubusercontent.com/664177/176442085-61fc8751-a7b9-489f-ad4f-deb416c60bca.png)|![Typed routes in navigation guards](https://user-images.githubusercontent.com/664177/176442089-b8523642-9cee-4d9f-b1ff-c9f8986fec02.png)| |-|-|-| #### CJS/MJS support for Node We now expose a few extra entry points for Node but kept the old ones as well to prevent any disruption to the existing users. You can find more information about this [in the corresponding pull request](https://togithub.com/vuejs/router/pull/1157). *** Please refer to [CHANGELOG.md](https://togithub.com/vuejs/router/blob/main/packages/router/CHANGELOG.md) for details. ### [`v4.0.16`](https://togithub.com/vuejs/router/releases/tag/v4.0.16) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.15...v4.0.16) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/router/blob/main/CHANGELOG.md) for details. ### [`v4.0.15`](https://togithub.com/vuejs/router/releases/tag/v4.0.15) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.14...v4.0.15) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/router/blob/main/CHANGELOG.md) for details. ### [`v4.0.14`](https://togithub.com/vuejs/router/releases/tag/v4.0.14) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.13...v4.0.14) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/router/blob/main/CHANGELOG.md) for details. ### [`v4.0.13`](https://togithub.com/vuejs/router/releases/tag/v4.0.13) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.12...v4.0.13) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/router/blob/main/CHANGELOG.md) for details. ### [`v4.0.12`](https://togithub.com/vuejs/router/releases/tag/v4.0.12) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.11...v4.0.12) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/vue-router-next/blob/master/CHANGELOG.md) for details. ### [`v4.0.11`](https://togithub.com/vuejs/router/releases/tag/v4.0.11) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.10...v4.0.11) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/vue-router-next/blob/master/CHANGELOG.md) for details. ### [`v4.0.10`](https://togithub.com/vuejs/router/releases/tag/v4.0.10) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.9...v4.0.10) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/vue-router-next/blob/master/CHANGELOG.md) for details. ### [`v4.0.9`](https://togithub.com/vuejs/router/releases/tag/v4.0.9) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.8...v4.0.9) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/vue-router-next/blob/master/CHANGELOG.md) for details. ### [`v4.0.8`](https://togithub.com/vuejs/router/releases/tag/v4.0.8) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.7...v4.0.8) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/vue-router-next/blob/master/CHANGELOG.md) for details. ### [`v4.0.7`](https://togithub.com/vuejs/router/releases/tag/v4.0.7) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.6...v4.0.7) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/vue-router-next/blob/master/CHANGELOG.md) for details. ### [`v4.0.6`](https://togithub.com/vuejs/router/releases/tag/v4.0.6) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.5...v4.0.6) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/vue-router-next/blob/master/CHANGELOG.md) for details. ### [`v4.0.5`](https://togithub.com/vuejs/router/releases/tag/v4.0.5) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.4...v4.0.5) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/vue-router-next/blob/master/CHANGELOG.md) for details. ### [`v4.0.4`](https://togithub.com/vuejs/router/releases/tag/v4.0.4) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.3...v4.0.4) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/vue-router-next/blob/master/CHANGELOG.md) for details. ### [`v4.0.3`](https://togithub.com/vuejs/router/releases/tag/v4.0.3) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.2...v4.0.3) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/vue-router-next/blob/master/CHANGELOG.md) for details. ### [`v4.0.2`](https://togithub.com/vuejs/router/releases/tag/v4.0.2) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.1...v4.0.2) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/vue-router-next/blob/master/CHANGELOG.md) for details. ### [`v4.0.1`](https://togithub.com/vuejs/router/releases/tag/v4.0.1) [Compare Source](https://togithub.com/vuejs/router/compare/v4.0.0...v4.0.1) Please refer to [CHANGELOG.md](https://togithub.com/vuejs/vue-router-next/blob/master/CHANGELOG.md) for details. ### [`v4.0.0`](https://togithub.com/vuejs/router/releases/tag/v4.0.0) [Compare Source](https://togithub.com/vuejs/router/compare/4d73be31f3e6781fcdcaecbd487c38084fd11f92...v4.0.0)

Vue logo

#### A more complete but lighter Router Today Vue Router 4 is officially released as stable. After 14 alphas, 13 betas and 6 release candidates, Vue Router v4 is ready to bring the best of routing to your Vue 3 applications with improved bundle size, TypeScript integration, new features and consistency improvements for modern apps. It has taken almost 2 years of work, around 1500 commits, [15 RFCs](https://togithub.com/vuejs/rfcs/pulls?q=is%3Apr+sort%3Aupdated-desc+label%3Arouter+is%3Aclosed), and the help of many users and their bug reports and feature requests to get here. Thank you all for your very much appreciated help! ##### Project Organization improvements Vue Router is now divided in three modules: - History implementation: handles the address bar and is specific to the environment Vue Router runs on (Node, Browser, Mobile, etc) - Router Matcher: handles the parsing of routes `/users/:id` and its ranking - Router: connects everything together and handle routing specific features like navigation guards ##### Dynamic Routing One the most wanted features on Vue Router is [Dynamic Routing](https://next.router.vuejs.org/guide/advanced/dynamic-routing.html). It makes the router more flexible and powerful and open possibilities for applications that were not possible before! This is possible thanks to an advanced path parsing with automatic ranking, allowing the router to *guess* what route should be matched based on the URL string representation, allowing user to define routes in any order. ##### Improved Navigation system The new navigation system is more consistent and improves the experience of Scroll Behavior to match native browser behavior. It also gives users almost more information about the status of a navigation and allow using that information to improve user experience through global UI elements like progress bars and modals. ##### More powerful Devtools Thanks to the [new Vue Devtools](https://chrome.google.com/webstore/detail/vuejs-devtools/ljjemllljcmogpfapbkkighbhhppjdbg), Vue Router is able to create more advanced integrations: navigation in the timeline and a complete route directory that helps you debug routes. ##### Better Navigation guards Say *good bye* to `next` and avoid easy-to-make mistakes inside navigation guards: return any value you were passing to `next`. The previous version is still supported to ease migration! More information [on the updated documentation](https://next.router.vuejs.org/guide/advanced/navigation-guards.html#global-before-guards). ##### Consistent encoding in routes Encoding has been adapted to make it consistent across different browsers and route location properties (`params`, `query` and `hash`). You don't need to encode these properties when passing them to `router.push()` and they will always appear decoded in the route locations (e.g. `$route` and `useRoute()`). ##### Small migration path Vue Router 4 focus on improving the existing Router while keeping a very similar API, migration should be short and almost limited to a few renames if you were using the basics of Vue Router. You can check the full migration guide [on the documentation](https://next.router.vuejs.org/guide/migration/index.html) #### The future of the Router Vue Router has been effectively stable for the past couple of months and makes it possible to now focus on: - Better Developer experience with existing tooling (Vetur, Vite, Devtools, etc) - Better integration with modern features like Suspense - RFCs to improve the existing API or bring new ones - Lighter versions of the router #### Trying It Out If you want to give Vue Router 4 a quick try, you can [check this CodeSandbox](https://codesandbox.io/s/vue-router-4-reproduction-hb9lh), this [Vite template with Tailwind CSS](https://vite-tailwind.esm.dev/about), or [use the CLI](https://cli.vuejs.org/) to get started. To Learn more about Vue Router 4, check out our [new documentation](https://next.router.vuejs.org/). If you are an existing Vue 2.x user, go directly to the [Migration Guide](https://next.router.vuejs.org/guide/migration/index.html). #### Supporting Vue Router Development If your company uses Vue Router, please consider supporting its development by [supporting me](https://togithub.com/sponsors/posva) 🙏 . It will mean a lot and really help me to keep working on improving the Vue Ecosystem. *** If you were already using the release candidate version of vue router, you can find the list of improvements on the [CHANGELOG.md](https://togithub.com/vuejs/vue-router-next/blob/master/CHANGELOG.md).

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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



This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 1 year ago

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

The artifact failure details are included below:

File name: package-lock.json
npm notice 
npm notice New major version of npm available! 8.19.3 -> 9.2.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.2.0>
npm notice Run `npm install -g npm@9.2.0` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: cloud_py_api@0.1.0
npm ERR! Found: vue@2.7.14
npm ERR! node_modules/vue
npm ERR!   vue@"^2.7.13" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vue@"^3.2.0" from vue-router@4.1.6
npm ERR! node_modules/vue-router
npm ERR!   vue-router@"^4.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-12-14T13_36_37_493Z-debug-0.log
renovate[bot] commented 1 year ago

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.