fix(deps): update dependency vuetify to v2 - autoclosed #631
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.5.16
->2.0.5
Release Notes
vuetifyjs/vuetify
v2.0.5
Compare Source
🔧 Bug Fixes
v2.0.4
Compare Source
🔧 Bug Fixes
v2.0.3
Compare Source
🔧 Bug Fixes
v2.0.2
Compare Source
🔧 Bug Fixes
v2.0.1
Compare Source
🔧 Bug Fixes
v2.0.0
Compare Source
v2.0.0 Arcadia
Welcome to the official version 2.0 release of Vuetify! Before getting into the actual release introduction, I wanted to take a moment of your time to talk about project sponsorship and a unique opportunity that I've been fortunate enough to be a part of.
Version 2.0 represents the culmination of 8 months of development. Through the combined efforts of numerous developers, we have been able to bring the largest update we have ever had — the framework has never felt better.
Github has recently released a new program called Github Sponsors, something I've been fortunate enough to receive a beta invite for. Some of you know that I currently run a Patreon campaign for the same purpose. With my invite, I have started to transition supporters to the new platform due to the amazing benefits that Github is offering. What that is in a nutshell:
With that being said, I wanted to quickly talk about the 3 pillars of support available with sponsorship and highlight how it can benefit developers and businesses that use Vuetify.
Single developer
Company
Enterprise
The generous fund matching program from Github provides a rare opportunity for me to be able to invest more into the Vuetify ecosystem and continue to provide developers with a polished and expansive library for Vue.
Thank you for your support and please consider sponsoring the project.
If you have any questions, please do not hesitate to reach out to me in the community. Thank you for using Vuetify!
—John
📖 Table of Contents
#Release Introduction
#Important Links
#New Components & Features
#Documentation Updates
#Upgrade Guide
#Release Notes
#Known Issues
#I need help! 🆘
💥 Release Introduction
Hello and welcome to the v2.0 release, Arcadia. It has been almost 8 months since development kicked off and I believe we have accomplished something very special. As described in my talk in last year's VueConf TO presentation, we have performed a massive overhaul to every aspect of the framework, making it easier to use and maintain.
This is only a small list of overall framework improvements from quality of life changes, to new features and functionality (outside of the MD2 improvements). The documentation has been massively updated with over 250 new examples, tons of updated information on how to use the framework's internals, details on long-term support, an extended roadmap and a better API display for components. We have also setup a process for exporting the component api for vetur so that it is easier for us to keep it up to date.
I have also teamed up with Vue Mastery to bring high-quality tutorials into the Vuetify ecosystem. This video series has been developed around using version 2, is taught by Ben Hong and is perfect for new and experienced Vuetify developers alike. Make sure to check it out!
Since early alpha, we have been working with the community on small and large projects to ensure we have an easy and managable upgrade process from v1.5. Kael has even created an eslint-plugin to make the process of upgrading to the new grid even easier. If you run into any issues that do not appear to be covered in the Upgrade guide, please reach out to a developer in the release migration channel.
I'd like to give a huge thank you to everyone for your unwaivering support and for enabling me to work on open source as a full-time job. For the first time in the framework's history, I feel like we have a solid base for maintaining and developing new features and I've never been more excited for the future. Finally, while this release was an effort by many Vuetify developers, I would like to send a special thank you to some that went above and beyond in ensuring the v2 release was as polished as possible. In no particular order:
Thank you everyone for using Vuetify!
—John
❗️ Important Links
Documentation
Becoming a Github Sponsor (supports the author, John)
Becoming a backer on OpenCollective (supports the development team)
Become a subscriber on Tidelift (supports the author, John)
Consulting with the author, John
Community discord
Twitter
Medium publication
Shop
🤚 FAQ
<v-card>
)boolean
true or false.⚡ New Components & Features
##### [🔗 **VAppBar**](https://vuetifyjs.com/components/app-bars) Brand new component that was created to better scope the functionality of `v-toolbar`. All existing scrolling techniques and **app** functionality from `v-toolbar` has been moved. New scrolling techniques such as collapsing bar, scroll shrink and more have been added.🔗 VBanner
Brand new component introduced in MD2. You can find more information in the banner specification.
🔗 VChipGroup
Brand new component for grouping multiple
v-chip
s together in a column or row based format.🔗 VColorPicker
Brand new component designed to making color selection a breeze. With 5 available formats, hex, hexa, rgba, hsla and hsva,
v-color-picker
can accommodate a wide variety of use cases.🔗 VFileInput
The long awaited and highly anticipated file upload component. The
v-file-input
is aimed to replacing the default functionality and behavior of a regular<input type="file">
. It features a multitude of customization options for tweaking the way selections are displayed, all of the available styling ofv-text-field
and more.Developers notes: You may be wondering about 2 things: built in upload support and drag-and-drop. There will be an upcoming second component,
v-upload
, that is designed to have a more visual interface for manipulating file uploads and will support xml requests. With its introduction, we will be bringing drag-and-drop to both upload components.🔗 VListItemGroup
Brand new component for grouping multiple
v-list-item
s together.🔗 VOverlay
A staple feature that was previously integrated as part of dialogs and navigation-drawers has been abstracted into its own component for consumption.
🔗 VSimpleTable
Meant to be a replacement for a generic
table
element.🔗 VSlideGroup
A new group component designed to provide the functionality of
v-item-group
within a custom slide interface.📃 Documentation Updates
🛠 Upgrade Guide
Version 2 contains non backwards compatible breaking changes. This includes previously deprecated functionality from v1.x.x. These breaking changes are noted in the console for the corresponding components.
The existing grid is still operational and has an eslint plugin to help with migration. This plugin can also be used to help upgrade to the new grid.
Upgrade now!
##### Bootstrap Vuetify must now be instantiated and passed to the initial Vue instance. This is similar to how **vue-router** and **vuex** are bootstrapped. ##### Vue-CLI 3 Vuetify plugin install ```js // v1.5 // src/plugins/vuetify.jsimport Vue from 'vue'
import Vuetify from 'vuetify/lib'
import 'vuetify/src/stylus/app.styl'
Vue.use(Vuetify, {
iconfont: 'md',
})
// src/main.js
import Vue from 'vue'
import './plugins/vuetify'
import App from './App.vue'
Vue.config.productionTip = false
new Vue({
render: h => h(App),
}).$mount('#app')
Full Install
A-La-Carte Install (vuetify-loader)
Framework
The following components are now lazy by default. This means they will not render their content until they are explicitly activated. This drastically improves performance but may not be wanted depending upon your application's needs (i.e. For SEO purposes). To return to the previous behavior, use the eager prop.
v-badge
v-menu
v-tooltip
v-dialog
v-bottom-sheet
vuetify/lib
is now compiled to es6. This means supporting IE requirestranspileDependencies
or similar to be used, along with@babel/polyfill
Theme
Now supports dark/light theme variants. The dark property has been moved into the theme property. Will dynamically change when toggling $vuetify.theme.dark. If only using one variant, you only need to define its colors.
In order to disable the theme style sheet creation, you must use the disable property of the theme object.
Icons
Icon and iconfont declaration is now scoped under the icons property.
If you want to use a custom iconfont, you must set it up in the initial Vuetify options now.
Goto (scrolling helper)
Import location has changed. Must be explicitly bootstrapped with the Vuetify instance to use in vue-router scroll-behavior. Example of how to do this here. Reference documentation for scroll-behavior usage here.
Lang
The translator function t is now nested under the lang property.
Grid
The grid has been rebuilt modeled after bootstrap. The existing grid still works and needs some slight modifications. Kael has created an eslint plugin to help with this process.
.text-xs-center
is nowtext-center
as it applies to all screen widths unless overridden.d-flex
no longer have extra flex rules applied. This can be done manually with.flex-grow-1
.fluid
→.container--fluid
.scroll-y
→.overflow-y-auto
.hide-overflow
→.overflow-hidden
.show-overflow
→.overflow-visible
.no-wrap
→.text-no-wrap
.ellipsis
→.text-truncate
.left
→.float-left
.right
→.float-right
<v-layout row>
should not be used as.row
is now part of the new grid instead (#7956)Use the following regex to update spacing classes:
Styles
The main framework styles are now imported automatically.
Must install the sass package
Do not install node-sass, it is not the correct library.
Typography
The root font-size (per MD2 specification) is now 16px.
Event names
All event names has been changed from camelCase to kebab-case:
update:searchInput
→update:search-input
update:inputValue
→update:input-value
update:miniVariant
→update:mini-variant
update:pickerDate
→update:picker-date
update:selectingYear
→update:selecting-year
tableDate
→update:table-date
update:returnValue
→update:return-value
Activators
v-tooltip
,v-menu
,v-dialog
,v-list-group
andv-bottom-sheet
must now be bound using the new v-slot syntax.Regular activator
Nested activator
Unit tests
Testing with Vuetify is now similar to that of vue-router and vuex.
Form Input Validation
All form inputs default to white when using the dark prop unless the application is explicitly set to dark mode.
Removed Component Properties
These are previous deprecations from earlier versions that have now been removed:
<v-text-field textarea>
will no longer render<v-textarea>
<v-select autocomplete>
will no longer render<v-autocomplete>
<v-select combobox>
will no longer render<v-combobox>
<v-select overflow>
will no longer render<v-overflow-btn>
<v-select segmented>
will no longer render<v-overflow-btn segmented>
<v-select editable>
will no longer render<v-overflow-btn editable>
Individual Components
These are the changes required for existing components.
v-app
.application
→.v-application
v-alert
v-carousel
v-btn
v-chip
v-bottom-nav
v-bottom-nav
tov-bottom-navigation
v-bottom-navigation
<v-btn>
colorv-bottom-sheet-transition
Developer notes: Was never explicitly listed in API
v-btn
v-card-media
v-carousel
v-chip
v-data-iterator
&v-data-table
Data table (and iterator) have been rewritten from the ground up to be both easier to use and to allow for more flexibilty in more advanced use cases. This has resulted in a number of breaking changes. Some of these are shared between both components while some are unique to each.
Shared
v-data-iterator
v-data-table
<tr>
element. Previously this was optional.<tr>
element so that you can define your own<td>
columns. To get back to a similar look as in 1.5, you will need a<td>
with colspan equal to the number of columns in your header.v-expansion-panel
et alv-expansion-panel
→v-expansion-panels
v-expansion-panel-content
→v-expansion-panel
v-expansion-panel-header
v-expansion-panel-content
v-footer
class="pa-0"
v-jumbotron
v-list
et alv-list-tile
→v-list-item
v-list-tile-action
→v-list-item-action
v-list-tile-avatar
→v-list-item-avatar
v-list-tile-content
→v-list-item-content
v-list-tile-title
→v-list-item-title
v-list-tile-sub-title
→v-list-item-subtitle
v-list-group
v-list-item
s in the activator slotv-list-item
for activatorsv-list-item-content
/v-list-item-title
etc insteadv-navigation-drawer
v-select
,v-autocomplete
,v-combobox
,v-overflow-btn
The item scoped slot value of
{ tile }
is now{ attrs, on }
. is now bound similar to thev-menu
activator slot.v-select
v-speed-dial
v-tabs
v-tabs-items
v-tabs
model when nested. Must have :value or v-model explicitly bound.Developer notes: The tabs-items component does not have to be provided and is only necessary for custom implementations.
v-text-field
vue-the-mask
.v-text-field
,v-select
,v-textarea
,v-autocomplete
,v-combobox
💯 Release notes
Below is a consolidated list of changes made in v2. Every component that has a MD2 specification has been updated to match (with the exception of the known issues below). Every component that has a MD1 specification (and not 2) has been re-verified and updated to ensure that it matches the previous spec.
Developer notes:
v-autocomplete
,v-combobox
andv-overflow-btn
all benefit from a11y updatesSheets
Sliders
Sparklines
Tabs
Text Fields
Developer notes:
v-select
,v-textarea
,v-file-input
,v-autocomplete
andv-combobox
all benefit from the updated style propertiesTextareas
Timelines
Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻️ 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.
This PR has been generated by Renovate Bot. View repository job log here.