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.

Sign up for GitHub

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

Jump to bottom

Update dependency vuetify to v3 #101

Closed
wants to merge 1 commit into from
Closed

Update dependency vuetify to v3 #101

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 31, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vuetify (source) 2.6.15 -> 3.3.3 age adoption passing confidence

Release Notes

vuetifyjs/vuetify

v3.3.3

Compare Source

🔧 Bug Fixes
🧪 Labs
  • VDataTable: loading prop causes scrollbar to appear (923f5b7), closes #​17462
  • VDataTable: unselect properly in single select strategy (30f7b81)

v3.3.2

Compare Source

🔧 Bug Fixes
🧪 Labs

v3.3.1

Compare Source

🔧 Bug Fixes
🧪 Labs
  • VDataTable: add item-selectable and select-strategy props (6348e9a)
  • VDataTable: set item-value default value to "id" (50dcd93), closes #​17422

v3.3.0

Compare Source

v3.3.0 (Icarus)

Welcome to the v3.3.0 release of Vuetify!

This MINOR release is meant to coincide with Vue v3.3 and includes a few new features and bug fixes.

The v-bottom-sheet component has hit labs and is ready for testing:

bottom sheets

It is a modified version of v-dialog that extends from the bottom of the screen.

The group composable's model now respects selection order:

group selection order

We cleaned up the Forms validation documentation and added greater control over when an input is validated.

form validation

The new lazy option skips validation on mount allowing you to avoid unnecessary rule invocation.

The following is a table of the different validation options:

validate-on= "input" "blur" "submit" "lazy"
On mount ✅ ✅ ✅ ❌
On input ✅ ❌ ❌ *
On blur ✅ ✅ ❌ *
On submit ✅ ✅ ✅ *

*Uses the behavior of whatever it's combined with.

In addition, we ported over auto-select-first from v2, added loading indicators to all Data Table variants, and added Data Iterators to labs.

The team is now shifting focus to v2.7 Nirvana-lts and v3.4 (Blackguard); while also preparing to move Date Pickers and Calendars to Labs and promoting Data Tables to the core framework. These updates bring Vuetify 3 dangerously close to feature parity with Vuetify 2 and will mark a major milestone in the Vuetify 3 release cycle.

Once we have completed the above, it will free up the team to work on shoring up our GitHub issues and adding new features and functionality. Speaking of issues, in preparation for LTS, the team has been on an absolute tear triaging and dispositioning:

image

We hope that you enjoy this release and we look forward to rounding out the year with some exciting updates.

Until next time,

John Leider

💪 Support Vuetify Development

Vuetify is an open source MIT project that has been made possible due to the generous contributions by our sponsors and backers. If you are interested in supporting this project, please consider:

📖 Table of Contents

❗️ Important Links

📑 Upgrade guide

  • The active-color prop on v-list-item is deprecated, just use color (they did the same thing anyway)
  • v-img now has an automatic width and height, so you can probably remove some flex styles and explicit dimensions

💯 Release notes

🚀 Features
🔧 Bug Fixes
🧪 Labs
BREAKING CHANGES
  • types: .d.ts imports have to be changed to .d.mts
  • types: minimum typescript version 4.7

🆘 I need help!

If you are stuck and need help, don't fret! We have a very large and dedicated community that is able to provide help 24/7. Come to the #vuetify-3-help channel.

v3.2.5

Compare Source

🔧 Bug Fixes

v3.2.4

Compare Source

🔧 Bug Fixes
🔬 Code Refactoring
  • framework: use shallowRef instead of ref for primitives (#​17316) (04c9699)
  • VAlert: normalize text slot and prop (49d44fa)

v3.2.3

Compare Source

🔧 Bug Fixes
🧪 Labs
🔬 Code Refactoring
  • framework: convert all component props to factory functions (#​17263) (b5d725b)

v3.2.2

Compare Source

🔧 Bug Fixes
🔬 Code Refactoring
  • VBtn: explicitly define onClick function (633f0b1)

v3.2.1

Compare Source

🚀 Features
  • defaults: simplify useDefaults usage (9b7b7b9)

v3.2.0

Compare Source

v3.2.0 (Orion)

Welcome to the v3.2 release of Vuetify!

The team has been hard at work on some exciting new updates and we're excited to finally get it into your hands!
Orion has a huge focus on improving the defaults engine and giving users more tools to customize their application. We started by adding support for global class and style defaults; then hooked it up to virtual components.

For example, you can set the default class for all v-btn components to be my-btn:

import { createVuetify } from 'vuetify'

export default createVuetify({
  defaults: {
    VBtn: {
      class: 'my-btn',
    },
  },
})

The same is possible for virtual components as well. Simply alias a core component and reference it by its name in the config object:

import { createVuetify } from 'vuetify'
import { VBtn } from 'vuetify/components/VBtn'

export default createVuetify({
  aliases: {
    MyBtn: VBtn,
  },

  defaults: {
    MyBtn: {
      color: 'primary',
      class: 'my-btn',
      variant: 'tonal',
    },
  },
})

Whenever you use the MyBtn component in any template it will be rendered as a v-btn with the default props applied:

<template>
  <my-btn>My Button</my-btn>
  <!-- <v-btn color="primary" variant="tonal" class="mt-btn">...</v-btn>-->
</template>

Finally, we made our defaults composable publicly available. Now you can hook your custom components into the defaults engine and configure your entire application from a single source.

<template>
  <div>
    I am {{ props.foo }}
  </div>
</template>

<script setup>
  import { useDefaults } from 'vuetify'

  const _props = defineProps({ foo: String })
  const props = useDefaults(_props)
</script>

defaults

The defaults composable also works with nested configurations. This works in any combination of virtual, custom, and core Vuetify components.

For example, you can create a custom component that modifies the default behavior of its children:

import { createVuetify } from 'vuetify'
import { VBtn } from 'vuetify/components/VBtn'
import { VCard } from 'vuetify/components/VCard'

export default createVuetify({
  aliases: {
    MyBtn: VBtn,
    MyCard: VCard,
  },

  defaults: {
    MyBtn: {
      color: 'primary',
      class: 'my-btn',
      variant: 'tonal',
    },
    MyCard: {
      border: true,
      variant: 'text',

      MyBtn: {
        color: 'secondary',
        variant: 'text',
      },
    },
  },
})

Some other big feature updates in this release include:

With v3.2 complete, the team is preparing for v2.7-lts (Nirvana) and the next v3 release, Icarus. We've recently updated our roadmap to be more transparent about our plans for the future; as well as improve the information about each release. Also, we've drastically improved the performance of the documentation and added new tools, such as 🎮Vuetify Play, to all component examples.

image

We hope that you enjoy this release as much as we have enjoyed working on it.

Until next time,

John Leider

💪 Support Vuetify Development

Vuetify is an open source MIT project that has been made possible due to the generous contributions by our sponsors and backers. If you are interested in supporting this project, please consider:

📖 Table of Contents

❗️ Important Links

📑 Upgrade guide

  • The title prop on v-tab is now text
  • The visible-items prop has been removed

💯 Release notes

🚀 Features
🔧 Bug Fixes
🧪 Labs
BREAKING CHANGES
  • VTab: The VTab title prop is now text
  • VVirtualScroll: visibleItems has been removed

🆘 I need help!

If you are stuck and need help, don't fret! We have a very large and dedicated community that is able to provide help 24/7. Come to the #vuetify-3-help channel.

v3.1.16

Compare Source

🔧 Bug Fixes
🔬 Code Refactoring
  • extract focusChild helper function (1646d67)
  • extract focusableChildren helper function (2531a83)
🧪 Labs

v3.1.15

Compare Source

🔧 Bug Fixes
🧪 Labs

v3.1.14

Compare Source

🔧 Bug Fixes
🧪 Labs

v3.1.13

Compare Source

This release may break some subcomponent defaults, for example VTabs > VSlideGroup should now just be set on VTabs instead.

🔧 Bug Fixes
🧪 Labs
🔬 Code Refactoring
  • defaults: skip merging deep if prev is undefined (c363981)
🔄 Reverts

v3.1.12

Compare Source

🔧 Bug Fixes

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.

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

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

@renovate
Copy link
Contributor Author

renovate bot commented May 31, 2023 •
edited
Loading

⚠ 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:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm notice 
npm notice New major version of npm available! 8.19.4 -> 9.6.7
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.6.7>
npm notice Run `npm install -g [email protected]` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/vue
npm ERR!   vue@"2.7.14" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vue@"^3.2.0" from [email protected]
npm ERR! node_modules/vuetify
npm ERR!   vuetify@"3.3.3" from the root project
npm ERR!   peer vuetify@"^3.0.0-beta.4" from [email protected]
npm ERR!   node_modules/vite-plugin-vuetify
npm ERR!     peerOptional vite-plugin-vuetify@"^1.0.0-alpha.12" from [email protected]
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/worker/97adde/a79fbd/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/worker/97adde/a79fbd/cache/others/npm/_logs/2023-06-07T09_12_30_753Z-debug-0.log

@renovate renovate bot force-pushed the renovate/vuetify-3.x branch from 1ead73c to a16c8e3 Compare June 7, 2023 09:12
@sjcl sjcl closed this Jun 7, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Jun 7, 2023 •
edited
Loading

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.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.

@renovate renovate bot deleted the renovate/vuetify-3.x branch June 7, 2023 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@sjcl