[pull] dev from buefy:dev #394
Open
Conversation
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
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
* Added mobileModal to Clockpicker Component (#3840) * Added mobileModal to Clockpicker Component * Added mobileModal to Timepicker Component * Input-id prop checkbox * feat: 🎸 Adding a new prop to set the id for inner input Adding a new prop to set the id for inner input for checkbox component * docs: ✏️ Adding helping data on checkbox api file * refactor: 💡 Changing prop name * Fix: Logo not displaying in the Sidebar documentation (#3838) (#3839) * Fix: Disabled radio button has cursor 'pointer' (#3826) * Fix: Sidebar image not displaying in the documentation (#3838) * Fix: Expired and broken websites in expo page (#3780) (#3845) * Number input null issue fix - #3698 (#3847) * number input value fix - #3698 * checks fix --------- Co-authored-by: Amal Mathew <122610766+amal-qb@users.noreply.github.com> * Numberinput: fix long-press breaking when disabled (#3860) * Numberinput: fix long-press breaking when disabled * Numberinput: fix long-press unit test * Update notification.js (#3867) Updated documentation for attribute `auto-close` from #3855 * Fix: Full width sidebar doesn't have a close button (#3802) (#3856) * Fix: Expired and broken websites in expo page (#3780) * Fix: Full width sidebar doesn't have a close button (#3802) * Fix: Full width sidebar doesn't have a close button (#3802) - format code * Fix: Full width sidebar doesn't have a close button (#3802) - Add documentation * fix: infinite loop on Datepicker (#3877) - Fixes the bug that `Datepicker` ended up with an infinite loop when a user tried to move focus onto an unselectable cell. * Bump Version From v0.9.23 to v0.9.24 * Fix: Validation error on Input not reset by programmatically correcting the value (#3884) (#3886) * fix(lib): Input not validate on value prop change - Fixes the bug that `Input` did not validate an updated value if `value` prop was updated from outside; i.e., without user interaction. Runs validation whenever `value` is changed from outside. It determines the update is from outside if `computedValue` and the new value are different. Intentionally uses `!=` instead of `!==`, because `computedValue` and `value` may be either string or number. * test(lib): test validation on Input - Introduces new test cases for `Input` that test validation runs on relevant events: - "input" event - "change" event - `value` prop is programmatically changed Also tests cases where the `Input` value has v-model binding. These tests make sure that the chain of events won't run validation twice on the same value. * Fix: Validation error on Field with multiple child components (addons) persists after value is corrected (#3883) (#3885) * fix(lib): validation error on addons persisted - Fixes the bug that a validation error on a `Field` that wraps multile child components (has addons) persisted. `Field` wraps its slot in another `Field` (wrapper) if the slot is consisting of multiple components. It used to propagate `newType` to the wrapper, but this prevented the type of the wrapper updated once `newType` was set due to the line: https://github.com/buefy/buefy/blob/6f41e91bd24dfef8f680f27313e07b488ddcfc1d/src/utils/FormElementMixin.js#L137 Propagates `type` instead of `newType` to the wrapper. * test(lib): add test for Field's type - Adds a new test case for `Field` that tests if `Field` containing multiple components (addons) reflects the validation status of a wrapped input. This verifies the fix of the bug that `Field` with addons did not update its validation status (`newType`) once it was set. * Add nearbyMonthDays prop support to Datetimepicker (#3881) * Add nearbyMonthDays prop support to Datetimepicker Add Datepicker component prop `nearby-month-days` to Datetimepicker component * FIX lint Datetimepicker.vue * Use Datepicker default behavior for nearbyMonthDays prop * Update datetimepicker api doc with nearbyMonthDays prop * Update Twitter and Sponsor Links (#3888) * Updated The Documentation's Twitter Link * Updated Sponsor Links * Update FUNDING.yml * Update Package Json * Add Workflow to Publish Buefy on PR to Master --------- Co-authored-by: julzELO <73643910+julzELO@users.noreply.github.com> Co-authored-by: Aarón J. Montes <32050436+ajomuch92@users.noreply.github.com> Co-authored-by: Amal Mathew <122610766+amal-qb@users.noreply.github.com> Co-authored-by: navedqb <109583873+navedqb@users.noreply.github.com> Co-authored-by: Sylvain Marty <10723351+SylvainMarty@users.noreply.github.com> Co-authored-by: Kikuo Emoto <kemoto@codemonger.io> Co-authored-by: Guillaume Mercey <guillaume.mercey@gmail.com>
* fix: dist not included in published package - Fixes the bug that no `dist` folder was included in the published package: #3890 (comment) Adds `prepare` script to `package.json` to make sure `build:lib` is run before publishing. One could insert `npm run build:lib` before `npm publish` in `npm_deploy.yml` file, but `prepare` script has a few more benefits that other publishing methods, e.g., npm install via GitHub, yalc, become available. * fix: bump CircleCI Node to v18.18 - Due to new `prepare` script, CircleCI now runs the `vetur` script that is incompatible with Node v8.x during `npm install`: #3891 (comment) Node v18.x should work. * fix: Date/time pickers' locale-dependent results - Fixes the issue that specs of date/time pickers failed depending on the locale of the machine running the tests. - `Datepicker.spec.js` fixes the locale to "en-US" - `Datetimepicker.spec.js` fixes the locale to "en-US" - `Timepicker.spec.js` fixes the locale, and hour format to "en-US", and "24" respectively - `DatepickerMonth` uses the local timezone to create date fixtures. It used to use UTC but should be the local timezone because `DatepickerMonth` deals with the local timezone. * fix: flaky test case of Numberinput - Fixes the issue that the test case "increments/decrements on long pressing exponentially" of `Numberinput` randomly failed. Uses Jest's fake timer instead of the real timer to make the behavior predictable. * fix: Numberinput checkHtml5Validity errors in tests - Fixes the issue that the spec of `Numberinput` printed error messages when it tried to call `checkHtml5Validity` of a default mock `Input`. Supplies a special mock `Input` that implements a fake `checkHtml5Validity` method. * chore: update spec snapshots - Updates outdated spec snapshots. The following changes were made since the last snapshots had been taken: - `Checkbox.spec.js.snap`: `id` was added - `Clockpicker.spec.js.snap`: `trigger-tab-index` was added to `Dropdown` - `Colorpicker.spec.js.snap`: - `trigger-tab-index` was added to `Dropdown` - `aria-modal` was removed - `Datepicker.spec.js.snap`: - `trigger-tab-index` was added to `Dropdown` - `aria-modal` was removed - `Dropdown.spec.js.snap`: - `role` was removed - `aria-modal` was moved to the inside `div` - `NavbarDropdown.spec.js.snap`: `navbar-dropdown` was split into `is-hidden-touch` and `is-hidden-desktop` - `Pagination.spec.js.snap`: `pagination-inpu` was introduced - `Sidebar.spec.js.snap`: hidden `button` was introduced - `StepItem.spec.js.snap`: attribute order was changed, maybe because `elementClass` was moved to `staticClass` in `TabbedChildMixin` - `Steps.spec.js.snap`: attribute order of `StepItem` was changed - `TabItem.spec.js.snap`: attribute order was changed, maybe because `elementClass` was moved to `staticClass` in `TabbedChildMixin` - `Tabs.spec.js.snap`: - `role` and `aria-orientation` were moved to the inside `ul` - `role`, `aria-controls`, and `aria-selected` of `a` were moved to surrounding `li` - attribute order of `TabItem` was changed - `Taginput.spec.js.snap`: `keep-open` became `true` by default - `Timepicker.spec.js.snap`: - `trigger-tab-index` was added to `Dropdown` - spec specified the locale to make outputs predictable - `Tooltip.spec.js.snap`: `span` became `div` - The following snapshots change but are not included: - `CarouselList.spec.js.snap`: I am sceptic about reproducibility, because it includes some information for coverage calculation - `Collapse.spec.js.snap`: I was not able to explain how the old snapshot was taken
* Fix: Expired and broken websites in expo page (#3780) * Fix: Full width sidebar doesn't have a close button (#3802) * Fix: Full width sidebar doesn't have a close button (#3802) - format code * Fix: Full width sidebar doesn't have a close button (#3802) - Add documentation * Fix eslint errors in pagination examples
* feat: add renderOnMounted prop for Modal - `Modal` introduces a new prop `renderOnMounted` that determines if DOM for the modal content is created on mounted whether modal is active or not. This flag is useful if you want to access DOM before first activating the modal. Also adds test cases for this prop. * docs: document renderOnMounted prop of Modal
* 🚧 2020-12-29 16:45:39
* 🚧 Add default value for dialog loading prop.
* 🚧 Add unit test for dialog loading.
* restore-snapshots:
git checkout -- src/components/carousel/__snapshots__/CarouselList.spec.js.snap
git checkout -- src/components/collapse/__snapshots__/Collapse.spec.js.snap
* 🚧 Change it to an internal state
* 🚧 Dialog loading
* 💡 document the new feature.
* 🚧 format code.
* 🚧 Restore StartLoadling.
* 🚧 changes function name.
* WIP: remove invalid code
* 🔥 remove "await" from test.
* 🔥 remove invalid code.
* 👌 update Dialog.spec.js.
* Fix: Expired and broken websites in expo page (#3780) * Fix: Full width sidebar doesn't have a close button (#3802) * Fix: Full width sidebar doesn't have a close button (#3802) - format code * Fix: Full width sidebar doesn't have a close button (#3802) - Add documentation * Fix eslint errors in pagination examples * Fix eslint errors in autocomplete and breadcrumb components
…to body (#3865) When Autocomplete is used as Taginput child, appended to body Dropdown position should be calculated from Taginput element as trigger.
- Fixes the issue that `Tag` did not accept objects as its `type` while objects actually work. Adds `Object` to acceptable types of `type`. issue #3887
- Fixes the issue that SVG icons were too large on Safari. See the
following comments for workarounds:
- #3872 (comment)
- #3872 (comment)
* fix(lib): update `build:scss` script - Updates the script `build:scss` that compiles scss files and minifies the resulting CSS file. It inserts the banner before compiling scss files, because some frameworks, e.g., Nuxt, complain about the `@charset "UTF-8"` not being at the top of the CSS file. FYI: `@charset "UTF-8"` is prepended by `sass` command.
* fix(lib): tooltip layout (appendToBody) - Fixes the issue that `Tooltip` is shown at a place slightly shifted from the expected one when `appendToBody` is `true`, and `position` is "is-top" or "is-bottom". Updates the absolute position of the anchor element (`tooltipEl`) instead of the `wrapper` element. See #3753 (comment) * fix(lib): Tooltip did not respond to resize - Fixes the issue that `Tooltip` did not respond to resizing when it was appended to body. Observes changes in the sizes of windown and the immediate parent element. See the comment: - #3753 (comment) * fix(lib): Tooltip was dislodge when Modal opened - Fixes the issue that a Tooltip was slightly dislodged when a Modal was just opened if the Tooltip was in the Modal and appended to body. This should have been caused by the CSS transition involving changes in the Modal size. Updates the position after the CSS transition of the closest `.animation-content` if such an element exists. See the comment: - #3753 (comment) Also fixes #3065
…ct-zip (#3844) Bumps [minimist](https://github.com/minimistjs/minimist) to 1.2.8 and updates ancestor dependencies [minimist](https://github.com/minimistjs/minimist), [mkdirp](https://github.com/isaacs/node-mkdirp), [cypress](https://github.com/cypress-io/cypress), [loader-fs-cache](https://github.com/viankakrisna/loader-fs-cache), [handlebars](https://github.com/wycats/handlebars.js) and [extract-zip](https://github.com/maxogden/extract-zip). These dependencies need to be updated together. Updates `minimist` from 1.2.0 to 1.2.8 - [Release notes](https://github.com/minimistjs/minimist/releases) - [Changelog](https://github.com/minimistjs/minimist/blob/main/CHANGELOG.md) - [Commits](minimistjs/minimist@v1.2.0...v1.2.8) Updates `mkdirp` from 0.5.1 to 0.5.6 - [Release notes](https://github.com/isaacs/node-mkdirp/releases) - [Changelog](https://github.com/isaacs/node-mkdirp/blob/main/CHANGELOG.md) - [Commits](isaacs/node-mkdirp@0.5.1...v0.5.6) Updates `cypress` from 3.4.1 to 12.8.1 - [Release notes](https://github.com/cypress-io/cypress/releases) - [Changelog](https://github.com/cypress-io/cypress/blob/develop/CHANGELOG.md) - [Commits](cypress-io/cypress@v3.4.1...v12.8.1) Updates `loader-fs-cache` from 1.0.2 to 1.0.3 - [Release notes](https://github.com/viankakrisna/loader-fs-cache/releases) - [Commits](https://github.com/viankakrisna/loader-fs-cache/commits) Updates `handlebars` from 4.5.3 to 4.7.7 - [Release notes](https://github.com/wycats/handlebars.js/releases) - [Changelog](https://github.com/handlebars-lang/handlebars.js/blob/master/release-notes.md) - [Commits](handlebars-lang/handlebars.js@v4.5.3...v4.7.7) Updates `extract-zip` from 1.6.7 to 1.7.0 - [Release notes](https://github.com/maxogden/extract-zip/releases) - [Commits](max-mapper/extract-zip@v1.6.7...v1.7.0) --- updated-dependencies: - dependency-name: minimist dependency-type: indirect - dependency-name: mkdirp dependency-type: indirect - dependency-name: cypress dependency-type: direct:development - dependency-name: loader-fs-cache dependency-type: indirect - dependency-name: handlebars dependency-type: direct:development - dependency-name: extract-zip dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Wesley Ford <wes@wesdevpro.com>
Bumps [@babel/traverse](https://github.com/babel/babel/tree/HEAD/packages/babel-traverse) from 7.8.4 to 7.23.5. - [Release notes](https://github.com/babel/babel/releases) - [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md) - [Commits](https://github.com/babel/babel/commits/v7.23.5/packages/babel-traverse) --- updated-dependencies: - dependency-name: "@babel/traverse" dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [@cypress/request](https://github.com/cypress-io/request) to 3.0.1 and updates ancestor dependency [cypress](https://github.com/cypress-io/cypress). These dependencies need to be updated together. Updates `@cypress/request` from 2.88.11 to 3.0.1 - [Release notes](https://github.com/cypress-io/request/releases) - [Changelog](https://github.com/cypress-io/request/blob/master/CHANGELOG.md) - [Commits](cypress-io/request@v2.88.11...v3.0.1) Updates `cypress` from 12.8.1 to 13.6.1 - [Release notes](https://github.com/cypress-io/cypress/releases) - [Changelog](https://github.com/cypress-io/cypress/blob/develop/CHANGELOG.md) - [Commits](cypress-io/cypress@v12.8.1...v13.6.1) --- updated-dependencies: - dependency-name: "@cypress/request" dependency-type: indirect - dependency-name: cypress dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [browserify-sign](https://github.com/crypto-browserify/browserify-sign) from 4.0.4 to 4.2.2. - [Changelog](https://github.com/browserify/browserify-sign/blob/main/CHANGELOG.md) - [Commits](browserify/browserify-sign@v4.0.4...v4.2.2) --- updated-dependencies: - dependency-name: browserify-sign dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* chore: update dependencies
- Bumps dependencies to versions as latest as possible without changing:
- Source code of the library, docs, and tests
- Build configuration: Webpack, Rollup, ESLint, etc.
→ We stick to Webpack v3.x
`babel-loader` is up to v7.1.5. This imposes Babel v6.x on us. `jest`
is also constrained by this, because `babel-jest` is up to v23.6.0.
`Rollup` is up to v2.79.1 because `rollup-babel-plugin` requires
`Rollup` < v3.
`lint-staged` stopped working even if I did not change the version.
There might be a magical configuration, but I decided to bump it to
the latest version v15.2.0 and rewrite `package.json`. Fortunately, it
is a Git hook that runs when changes are going to be commited, so it
won't matter to build artifacts.
Please refer to PR #3929 for more details.
* test(lib): refresh snapshots
- Refreshes snapshots affected by the last updates of dependencies.
- Fixes the issue that sort icons on Table overlapped or were clipped by next columns. Since sort icons were absolutely positioned and placed at the right side of the column label texts, the icons overlapped or were clipped by the right columns when columns were packed. This commit changes the anchor element for sort icons to `<div class="th-wrap">` elements that wrap the column label texts and absolutely places sort icons ON the right end of the `<div class="th-wrap">` elements instead. If the column `is-numeric`, the sort icon is placed on the left end of the `<div class="th-wrap">` element, otherwise the sort icon overlaps the column label text. Similar problems occurred when the `sort-multiple` option was turned on. Applying the above solution to the delete buttons of sort indicators did not work well. The delete buttons were torn apart from the sort icons since the sort icons aligned with the normal flow of the column label texts. I decided to group the sort icon, number, and delete button as `multi-sort-icons` so that they do not split. `multi-sort-icons` is placed in the normal flow of the column label texts and moves to the next line if the column is packed. issues - #2886 - #3034
* fix: dist was not built before publish to npm - Fixes the issue that the `dist` folder was not built before publishing to npm. `package.json` used to include `prepare` script that runs `build:lib` script and `npm ci` built the `dist` folder. I removed `prepare` script in the commit ccbdc8e because `npm install` took very long. So we have to run `build:lib` before `publish` now. * chore(gha): update npm_deploy dependencies - Updates dependencies of `npm_deploy` GitHub Actions workflow: - Bump Node to v18.x - Bump actions/checkout to v4 - Bump actions/setup-node to v4
- We had a problem with GitHub Actions workflow for npm publish.
…ices (#3961) (#3962) * fix(lib): dislodged hoverable dropdown on mobile screen - Fixes the issue that the contents of a hoverable `BDropdown` was displayed at a wrong position on a mobile (narrow) screen. I initially thought to cancel the effect of `is-hoverable` on narrow screen whether it is on mobile devices or not. But it contradicted to the documentation of `Dropdown`, and I decided to keep the original statement about the behavior of "hover" trigger. #3961 (comment) Since hover events do not make sense on touch devices. "hover" trigger now works like "click" trigger on touch devices, and dropdown contents are shown in a modal when the screen is narrow. To detect actual touch devices, the trigger element of `BDropdown` now handles touch events: touchstart, touchmove, and touchend. The contents of `BDropdown` with "hover" trigger on a touch device pops up only when the trigger is tapped; i.e., at touchend immediately following touchstart. `BDropdown` bears `.is-touch-enabled` class if the trigger is tapped. The modal style is applied when the screen is narrow and: - `.is-hoverable` is disabled - or `.is-touch-enabled` is enabled The `:hover` state is only applied if touch is not enabled (`:not(.is-touch-enabled)`). Delays to reset `isTouchEnabled` to avoid glitches; I observed a ghost of the dropdown menu under the trigger on a touch device. I avoided `@media (hover: hover)` condition for the `:hover` state, because it might cause problems on 2-in-1 devices: #3962 (comment) "hover" trigger precedes "click" trigger in case both are enabled. * feat(docs): dropdown "hover" behavior on touch devices - `ExSimple` example of `BDropdown` explains the new behavior of `BDropdown` with "hover" trigger on touch devices. --------- Co-authored-by: Wesley Ford <wes@wesdevpro.com>
- Fixes the issue that no dropdown showed up if the data array was empty and only the footer slot was registered. Display Autocomplete list if footer slot is registered
* docs: update CHANGELOG.md - Prepends changes from v0.9.27 to v0.9.28. Tells v0.9.26 was withdrawn due to missing `dist` folder in the package. * docs: link CHANGELOG to relevant issues - `CHANGELOG.md` now has working links to relevant issues. I replaced the issue numbers in `CHANGELOG.md` with the Python script available from the following repo: https://github.com/kikuomax/link-commit-hash issue #3960
* feat(docs): add how to install @ntohq/buefy-next - `Home` shows how to install `@ntohq/buefy-next` for people who need Vue 3 support. issue #3967 * feat(docs): add link to ntohq/buefy-next repo - Adds a link to `ntohq/buefy-next` repo to `Home`. issue #3967 * chore(docs): replace "work in progress" - Replaces "work in progress" with "official fork in develoment" on `Home`. Aligns it with the expression used in `README.md`. * feat(docs): add link to ntohq/buefy-next to Start - Adds the link to `ntohq/buefy-next` repo to `Start`. This addresses the following comment: #3967 (comment) issue #3967 * fix(docs): Home overflowed on narrow screen - Fixes the issue that `Home` overflowed and had contents not centered on narrow screens; e.g., mobile portrait, which was pointed at in the following comment: #3969 (comment) There were two problems: 1. The width of the code snippet was not constrained 2. `display: flex` style of `div.hero-body` was problematic Solutions: 1. Adds `max-width: 100%` to `.npm` class. 2. Replaces `display` style of `div.hero-body` to `block` by adding `.is-block` Bulma class. `flex` tried to expand the boundary of `div` to contain the code snippet `$ npm install @ntohq/buefy-next`, and then `Home` ended up with being wider than the screen and having dislodged contents.
#3971) (#3986) * fix(lib): lower Vue version to 2.6.11 - Fixes the issue that the pagination control of `BTable` rendered as "undefined". It seems that some code generated by `vue-template-compiler` v2.7.x does not work on Vue v2.6.x, but that generated by `vue-template-compiler` v2.6.x seems to work both on v2.6.x and v2.7.x. According to the comment of a Vue core team member, we have to use `vue-template-compiler` corresponding to the minimum Vue version we want to support; i.e., v2.6.11 for Buefy. See #3971 (comment) So lowers the version of `vue` and `vue-template-compiler` to 2.6.11. issue #3971 * fix(lib): percentage width on columns doubly applied - Fixes the issue that column widths were doubly applied when they were given in percentage ('%'). Interestingly, percentage widths have effect on `<th>` elements in contrast to absolute values; e.g., 200px. So we won't apply the column widths given in percentage to `.th-wrap` elements to prevent widths from being doubly applied. issue #3971
Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.15.3 to 1.15.4. - [Release notes](https://github.com/follow-redirects/follow-redirects/releases) - [Commits](follow-redirects/follow-redirects@v1.15.3...v1.15.4) --- updated-dependencies: - dependency-name: follow-redirects dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…props (#3862) * Expose isActiveDetailRow method in table component column slot props
* chore(docs): update table column docs for default slot - Adds `toggleDetails` and `isActiveDetailRow` to the props provided by the scoped default slot of `TableColumn`. Addresses the comment: #3862 (review)
fix(lib): potential leak and call after unmount - `NumberInput` clears the timeout on unmount to make sure it is not called after unmount - `Sidebar` clears the timeout on unmount to make sure it is not called after unmount - `SliderThumb` removes listeners in case they might be left in overlooked edge cases fix(docs): dangling listeners - `TheNabver` and `Documentation` removes listeners on unmount
* docs: update CHANGELOG on v0.9.28 - Adds changes in v0.9.28 since `CHANGELOG` was last updated.
) * Clear timing events and event listeners before component unmounts - The following components clear timeouts before unmounted so that timeout callbacks won't access unmounted component instances: - `Autocomplete` - `ColorpickerHSLRepresentationSquare` - `ColorpickerHSLRepresentationTriangle` - `Dropdown` - `Slider` - `Taginput` - `Tooltip` * feat(lib): revert unnecessary clearTimeout - Reverts unnecessary `clearTimeout` calls in: - `Dialog`: #4000 (comment) - `Loading`: #4000 (comment) - `Modal`: #4000 (comment) - `NotificationNotice`: #4000 (comment) --------- Co-authored-by: Kikuo Emoto <kemoto@codemonger.io>
- Adds changes made since `CHANGELOG.md` was last updated.
Bumps [ip](https://github.com/indutny/node-ip) from 1.1.8 to 1.1.9. - [Commits](indutny/node-ip@v1.1.8...v1.1.9) --- updated-dependencies: - dependency-name: ip dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…) (#4019) * fix: Tooltip did not work in SSR due to AbortController Fixes the bug that `Tooltip` did not work in Server Side Rendering (SSR) due to `window.AbortController` use; i.e., no `window` is available in SSR. Moves `window.AbortController` access inside the `window` availability check. * docs: update CHANGELOG Adds unreleased entry for v0.9.29. Lists the fix of the `window.AbortController` use in SSR.
…h form in modal (#4018) (#4021) * fix(lib): infinite Field updates - Fixes the bug that `Field` caused infinite recursions when both `grouped` and `horizontal` attributes were `true`, and a validation error was set. There were circular updates of the `newMessage` data field and the `message` prop of the child `Field`s. To break the loop, `watch` of the `message` prop makes sure that the contents of the new value are different from the `newMessage` data field before updating `newMessage`. Simple identity check won't work because `message` receives a brand new array every time. * test(lib): add test cases for Field with grouped and horizontal - Adds new test cases that test `Field` with `grouped` and `horizontal` attributes `true`. The test would never stop due to infinite recursions if the previous fix were not applied. * docs(CHANGELOG): update unreleased log - Adds the fix of `Field` freezing due to infinite recursions. - Explains the issue that remains after fixing the frozen Field bug. * chore(docs): add warning on grouped and horizontal (Field) - Adds warnings of not mixing `grouped` and `horizontal` props of `Field`.
Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.15.4 to 1.15.6. - [Release notes](https://github.com/follow-redirects/follow-redirects/releases) - [Commits](follow-redirects/follow-redirects@v1.15.4...v1.15.6) --- updated-dependencies: - dependency-name: follow-redirects dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* chore: bump version to 0.9.29 * docs(CHANGELOG): release 0.9.29
- The installation instruction of Buefy for Vue 3 (buefy-next) aliases `@ntohq/buefy-next` as `buefy`. This will mitigate the migration cost for users of buefy-next that will eventually be released as buefy@1. See: https://www.reddit.com/r/vuejs/comments/wg1b0u/comment/kttd5sa/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
- Fixes the CodePen URL in the BUG_REPORT issue template.
Bumps [express](https://github.com/expressjs/express) from 4.18.2 to 4.19.2. - [Release notes](https://github.com/expressjs/express/releases) - [Changelog](https://github.com/expressjs/express/blob/master/History.md) - [Commits](expressjs/express@4.18.2...4.19.2) --- updated-dependencies: - dependency-name: express dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
unpkg is not reliable for a production project. This change ensures newcomers opting for standalone will start on a more reliable base. See discussion #4033
* Fix: broken link to bulma docs * Fix: update link
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )