forked from buefy/buefy
-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix [Clockpicker, Timepicker]: Vue Compat: deprecation INSTANCE_ATTRS…
…_CLASS_STYLE (#16) (#210) * feat(lib): mix CompatFallthroughMixin in TimepickerMixin - `TimepickerMixin` mixes in `CompatFallthroughMixin`, because both hosts `Clockpicker` and `Timepicker` provide fallthrough behavior. * feat(lib): add compat fallthrough to Clockpicker - `Clockpicker` introduces a new prop `compat-fallthrough`, which determines if the `class`, `style`, and `id` attributes are applied to the root `<div>` element or the underlying `BInput` component. Since Vue 3 changed the fallthrough behavior, `Clockpicker` became incompatible with that of Buefy for Vue 2. The default value of this prop is configured by the `defaultCompatFallthrough` config option, which is `true` by default (compatible with Buefy for Vue 2). * test(lib): test compat-fallthrough prop of Clockpicker - Tests the fallthrough behavior of `Clockpicker` * feat(lib): add compat fallthrough to Timepicker - `Timepicker` introduces a new prop `compat-fallthrough`, which determines if the `class`, `style`, and `id` attributes are applied to the root `<div>` element or the underlying `BInput` component. Since Vue 3 changed the fallthrough behavior, `Timepicker` became incompatible with that of Buefy for Vue 2. The default value for this prop is configured by the `defaultCompatFallthrough` config option, which is `true` by default (compatible with Buefy for Vue 2). * test(lib): test fallthrough behavior of Timepicker - Tests the fallthrough behavior of `Timepicker` * chore(docs): explain compat-fallthrough of Clockpicker * chore(docs): explain compat-fallthrough of Timepicker * docs(CHANGELOG): explain compat-fallthrough of Clockpicker and Timepicker
- Loading branch information
Showing
8 changed files
with
138 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters