The Bolt Design System provides robust Twig and Web Component-powered UI components, reusable visual styles, and powerful tooling to help developers, designers, and content authors build, maintain, and scale best of class digital experiences.
MIT License
Bot releases are hidden (Show)
Published by sghoweri over 5 years ago
<bolt-table>
component to now be a full blown web component! đ #1138showerrors
event listener to allow form inputs to auto-display input errors by emitting a showerrors
custom Javascript event. #1177preact
version of <bolt-tooltip>
component to lit-html
to fix disappearing first tooltip icon issue on IE/Edge. #1133TESTING.md
testing steps via #1206 - thanks @joekarasek!getModifiedSchema()
to bolt-base renderer, remove from image and blockquote components.@bolt/core
styles to add a few missing !default flags to allow Sass config options to be more easily updated and extended. #1148loop
is set to true. #1219devDependencies
or peerDependencies
. Addresses install and build issues flagged when testing the Drupal Lab example with the team and encountered these unexpected issues. #1189attributes
that had been occurring when list (list, ol, and ul) components contained empty elements #1188<bolt-list>
's web component so the flex
option is styled and behaves the same way as the Twig-template version. #1111.boltrc
config to automatically open a new tab when booting up a new dev server instance.As a future update this ideally could be customized per developer's personal preference via a local config file that gets merged with these repo-specific defaults -- one that isn't version controlled
maxItemsPerRow
has been renamed to max_items_per_row
.align
has been updated to valign
to clearly indicate vertical alignment.border
has been updated to borderless
and its default set to false
.Published by sghoweri over 5 years ago
Bolt v2.5.1 was a fast-follow version bump to v2.5.0 due to a small NPM publishing issue that had occurred during the initial v2.5.0
release. No other functional changes were included -- just a global version bump of all related packages to ensure everything got published to NPM as expected.
Published by sghoweri over 5 years ago
This is a small hotfix release to address two integration issues identified:
@bolt/components-action-blocks
package #1198gcd
Twig function. #1196No API or code changes from this update should be required other than using the latest packages updated with this release.
@bolt/[email protected]
@bolt/[email protected]
@bolt/[email protected]
@bolt/[email protected]
@bolt/[email protected]
This update temporarily re-adds a action-block.twig
template to the action blocks package in order to fix a broken template path to an internally used Twig template recently renamed.
Refactored the recently added gcd
custom Twig function to now work in PHP environments where the gmp
PHP extension isn't installed. Additionally, this update also updated the BoltCore
Class in the core-php
package to now correctly include the new gmp
Twig function that was needed.
This fix also updates the BoltExtra
Class and splits the code up into two sets of custom Twig extensions:
BoltCoreCompat
which adds Drupal-specific Twig extensions and support to BoltBoltExtras
which adds custom Twig extensions used internally on the docs siteWith this update, the Twig environment used by our Jest tests even more closely resemble Drupal to help catch issues like this from reoccurring.
Published by sghoweri over 5 years ago
This is a small hotfix release which updates the package.json
files for several Bolt components / related NPM packages to no longer use devDependencies
or peerDependencies
. This addresses unexpected install and build issues when testing out the v2.4.2 release of Bolt in our Drupal Lab example (ie. installs from outside of the normal monorepo install / build context).
No API or code changes from this update should be required other than using the latest packages updated with this release.
devDependencies
and/or peerDependencies
to use dependencies
instead so packages get installed correctly.quick
Jest config)Note: this update should help better test for issues like this in the future (ie. installing, building, and deploying Drupal Lab)
## More Commonly Installed
- @bolt/[email protected]
- @bolt/[email protected]
- @bolt/[email protected]
- @bolt/[email protected]
- @bolt/[email protected]
- @bolt/[email protected]
- @bolt/[email protected]
- @bolt/[email protected]
- @bolt/[email protected]
- @bolt/[email protected]
## Less Commonly Installed / Related Dependencies
- @bolt/[email protected]
- @bolt/[email protected]
- @bolt/[email protected]
- @bolt/[email protected]
- @bolt/[email protected]
- [email protected]
- @bolt/[email protected]
- @bolt/[email protected]
- @bolt/[email protected]
Published by sghoweri over 5 years ago
This is a hotfix for the latest v2.4.x
-version of Bolt which updates the video component's Javascript to prevent an IE 11-specific bug from occasionally occurring that could result in the Brightcove video player initializing multiple times.
Note: these video player updates had already been part of the larger batch of component updates slated for an upcoming Bolt release -- this hotfix simply fast tracks a subset of those changes.
Note: this video update is largely identical to the updates backported and released in v2.3.3.
Brightcove changed their best practices for referencing a video player and for delayed player instantiation around v6.12 - v6.18. Our implementation needed to be updated to adhere to the new standards to avoid the confusing initialization issues mentioned in BC's release notes (see 6.18.3).
Since the code change on Brightcove's side, many of our videos worked fine, but we've been plagued by intermittent bugs, especially around plugins. These updates should fix that.
The key changes are:
data-account
, data-player
, or data-video-id
attributes on first render of the <video-js>
element or videos will auto-initialize. Add them on rendered()
just before calling bc()
. (code)bc()
to prevent re-initializing the video on re-render when attributes are added. (code)data-setup
. It's a Video.js prop that will confuse Brightcove. Instead pass those configuration options to the Brightcove function itself. (code)<video-js>
not <video>
, new best practice from Brightcove to avoid flash of native video controls. (code)videojs.getPlayer(id)
not videojs(id)
. The latter can cause Video.js to initialize. (code)In addition to the video component fix, this hotfix release also included a handful of other DevOps-related fixes that didn't require publishing any other additional packages.
These updates include fixing a failing Jest test for the Navbar component + fixes to Nightwatch.js test reporting logic so the build status is correctly reported + the browser screenshots captured show up again.
Published by sghoweri over 5 years ago
This is a hotfix for the older v2.3.x
-version of Bolt (originally released in January 2019) which updates the video component's Javascript to prevent an IE 11-specific bug from occasionally occurring that could result in the Brightcove video player initializing multiple times.
Note: these video player updates had already been part of the larger batch of component updates slated for an upcoming Bolt release -- this hotfix simply fast tracks a subset of those changes.
Brightcove changed their best practices for referencing a video player and for delayed player instantiation around v6.12 - v6.18. Our implementation needed to be updated to adhere to the new standards to avoid the confusing initialization issues mentioned in BC's release notes (see 6.18.3).
Since the code change on Brightcove's side, many of our videos worked fine, but we've been plagued by intermittent bugs, especially around plugins. These updates should fix that.
The key changes are:
data-account
, data-player
, or data-video-id
attributes on first render of the <video-js>
element or videos will auto-initialize. Add them on rendered()
just before calling bc()
. (code)bc()
to prevent re-initializing the video on re-render when attributes are added. (code)data-setup
. It's a Video.js prop that will confuse Brightcove. Instead pass those configuration options to the Brightcove function itself. (code)<video-js>
not <video>
, new best practice from Brightcove to avoid flash of native video controls. (code)videojs.getPlayer(id)
not videojs(id)
. The latter can cause Video.js to initialize. (code)Published by sghoweri over 5 years ago
This is a small follow-up to the v2.4.0
release that rolls back a handful of upcoming v2.5.0 updates.
With this update, the following components have been bumped to v2.4.1 (all others remain at 2.4.0):
@bolt/components-table
@bolt/components-action-blocks
@bolt/components-tooltip
@bolt/components-list
Published by sghoweri over 5 years ago
The new @bolt/analytics-autolink
helper library streamlines the process of integrating any existing / future Bolt components with Google Analytics Linker to more easily track outbound URLs. Includes automated tests + docs in the README. #1125
<bolt-blockquote>
via #984<bolt-blockquote
author-name="Michelangelo di Lodovico Buonarroti Simoni"
author-title="Renaissance Artist"
author-image="/images/placeholders/500x500.jpg"
>
<img slot="logo" src="/images/content/logos/logo-paypal.svg" alt="PayPal Logo">
<p>The greater danger for most of us lies not in setting our aim too high and falling short...</p>
<p>In fact, the greater danger is setting our aim too low and achieving our mark.</p>
</bolt-blockquote>
<bolt-chip>
via #1078<bolt-chip>
Text of the chip
</bolt-chip>
<bolt-image>
via #1032<bolt-image
src="https://boltdesignsystem.com/images/placeholders/tout-4x3-climber.jpg"
alt="A Rock Climber"
ratio="4/3"
placeholder-color="#D3D3D3"
placeholder-image="http://placehold.it/400x300"
></bolt-image>
init
Custom Twig FunctionThis new init
custom Twig function added to core-php
is part of ongoing architectual efforts to standardize how Twig / Web Components are built, taking the component's initial data, API, and defaults into consideration.
The updates from #1083 adds a new, automatically generated (always up to date) component status board to the Pattern Lab's main overview page.
With the new Yeoman Component generator added, new components can be easily spun up automatically using the same base structure and coding standards as a starting point. #1101
Added a new Algolia-powered docs site search to help moving around the Bolt Design System documentation site. #1132
Before:
After
This sets up the GitHub Checks API for collecting information about a commit's build info. It removes the need to have Bolt Bot comment on PRs for deploy info and moves it to the "Checks" tab above and also allows more information to be shown over in that tab. #1025
Upgraded the grid component to handle more complex layouts with versatile breakpoint options. #1047
Note: You can use this image as an reference to create some common layouts for testing.
Added the capability to server-side pre-render Bolt web components via JSDOM through a new experimental @bolt/ssr-server
package.
While there's still some work to be done before rolling this out for mass consumption on the backend (currently disabled in the code that's live), this is a significant milestone for many future endeavors in major improvements to content authoring, component flexibility, platform interoperability, code maintainability and more! #1097
cover
prop, used when an image needs to fill its container, i.e. object-fit (commit). #1032no_lazy
(commit), placeholder_color
, placeholder_image
, and ratio
props (commit) for Web Component use only.Note: While lazyloading still works, further lazyload-related improvements are in the works. Also, keep an eye on BDS-1132 for updates on adding support for handling inline-block images in a future Bolt release.
cover
prop, fix lazyload logic (commit).max-width
spec added to the component docs #1136content
and pinned_content
(see deprecation notes below)display
prop to handle inline
and flex
links. Links are inline
by default. Also added valign
prop for flex
links.@bolt/build-tools
Now ExtendableThe updates in #1128 add a new configureWebpack
advanced config option to the Bolt Build Tools .boltrc
config to allow extending the default Webpack config generated with additional plugins, module configs, etc via weback-merge.
@bolt/build-tools
. Added the ability to update the icon componentâs schema when icon assets are added / removed automatically + export list of available icons to a separate JSON file for better CMS integrations. #1020bolt-border-radius()
Sass function and mixin + new corresponding utility classes for better scalability and consistency. #1110bolt-ie11-only
for writing CSS that only applies to IE11. #1055<bolt-icon>
as expected. #1064items
propitems
to pinned_content
?{% include "@bolt-components-band/band.twig" with {
content: content,
items: [
{
position: {
align: "end",
valign: "center",
row_start: 1,
column_start: 1,
column_end: 12,
},
content: pinned_share,
},
]
} only %}
pinned_content
prop{% include "@bolt-components-band/band.twig" with {
content: content,
pinned_content: {
upper: [
{
content: pinned_share,
align: "end",
},
],
}
} only %}
imageAttributes
, useAspectRatio
, width
, and height
propsimageAttributes
is now no longer required. Previously this had only been used internally inside the background image component.useAspectRatio
: use the new ratio
prop insteadheight
and width
props: the new ratio
prop now takes care of the previous need for these two props.Published by sghoweri over 5 years ago
This is a hotfix release that patches two issues with the original v2.3.x release:
Big shoutout to @mikemai2awesome and @remydenton for their help getting these fixes in with a super quick turnaround!
Published by sghoweri over 5 years ago
This is a hotfix release that patches two high priority bugs with with the original v2.3.0 release:
yarn
reference in an NPM script that gets automatically run when installing the older version of the @bolt/components-icons
package (fix now switches the command to npm
for compatibility) #1107@bolt/components-image
Twig template to fix an issue related to auto-escaping #1108Extra shoutout to @remydenton for his help getting the ball rolling on both of these fixes!
Published by sghoweri over 5 years ago
@bolt/analytics-autolink
to make it easy wiring up Bolt components with Google Analytics Linker plugin. This makes it much easier to track the analytics for components with external domain URLs. #1125Note:
While lazyloading still works, but we need a better implementation in the future. Currently, on web components, lazy images are revealed right after render. Say we wanted to load only in-view images, this implementation would not suffice.
We'll be adding the option for inline-block images in a follow-up update. This will be handled in BDS-1132.
Background Image #1032
Added automated testing and updated docs for the Action Blocks component #1106
Added tests for the logo component as part of the bug fix addressed in #1123
Added basic testing coverage + updated docs for the Pagination component. #1105
Added documentation for usage of full-bleed background images. #1113
Bolt Icons: Added Jest tests to confirm the Icon build process + ability to add custom icons to Bolt is working as expected #1102
Background Shapes: Added automated jest testing + manual testing steps #1045
Bolt Link: Added display
prop to handle inline
and flex
links. Links are inline
by default. Also added valign
prop for flex
links.
Bolt Band
Bolt Blockquote: Extended and revamped the existing bolt-blockquote component so that blockquotes can now be rendered using Twig templates and web components. #984
Bolt Button
Add JEST test and documentation for testing to bolt-ol and bolt-ul components. #1054
Bolt Link
Bolt Icon
Bolt Image
Bolt Figure
Bolt Chip
Background Video Demo
Bolt Chip List
<bolt-list>
component. #1080Bolt Card: Added documentation and tests for the bolt-card component #1094
Bolt Ratio: Refreshes the ratio component's internals + adds testing coverage support via Jest (including visual regression testing) #1093
Bolt Band: Simplified pinned content feature in the band component for easier implementation. #1088
content
and pinned_content
(see deprecation notes below)Bolt Text: Added tests and docs for the now public bolt-text
web component.
Bolt Share: Added automated tests and manual testing steps for share component. #1127
Drupal Lab: Updated Bolt's example integrations with Drupal Lab + with Vue to use the latest Bolt / NPM dependencies + fix minor issues. Should also fix the error reported in #1092. #1095
Bolt Icons: added developer documentation on how to add custom SVG icons to a specific site using Bolt #1135
Misc updates and enhancements to the Bolt docs site + Pattern Lab UI. #1145
Adds search to the Bolt documentation site, powered by Algolia. #1132
Updated the core-php phpunit dependency to move it to being a devDep to address an install error in Drupal #1141
Updated the Bolt Build Tools configuration + PHP logic to automatically enable server-side rendering in prod mode, disable in local dev mode, and provide a new enableSSR config option to allow SSR to be manually be enabled / disabled (overriding the default auto behavior). #1131
Ungrouped list-like component folder organization per team feedback #1134
Adds a new configureWebpack
advanced config option to the Bolt Build Tools .boltrc
config to allow extending the default Webpack config generated with additional plugins, module configs, etc via weback-merge. #1128
New architectural pattern + init
custom Twig function to standardize on the different considerations when building out a component's data structure and API. With these updates in #1089 , a significant amount of code will no longer be written every time a new Bolt component is created / refactored:
Added the bolt-border-radius()
Sass function and mixin + new corresponding utility classes for better scalability and consistency. #1110
Updated the component status board logic to support using a new (optional) pattern-alias config when automatically matching up a component with the component's main viewall page in Pattern Lab. #1126
Added developer docs on the different types of Bolt releases #1119
Web Component Server Side Rendering (SSR): Added the capability to server-side pre-render Bolt web components via JSDOM through a new experimental @bolt/ssr-server
package. While there's still some work to be done before rolling this out for mass consumption on the backend, this is a significant milestone for many future endeavors in major improvements to content authoring, component flexibility, platform interoperability, code maintainability and more! #1097
Component Status Board #1083
Renamed several existing component folders in Pattern Lab in order to automatically match up with the names of the package names (what things are called once they are published to NPM) #1084
Upgrade Nightwatch.js testing setup to allow developers to run Nightwatch tests locally #1077
Major upgrades to Jest to support testing web component rendering in a browser and web page instance that's generated automatically, in addition to adding the ability to run visual regression tests on these. #1082
Added documentation for setting up Xdebug to debug the PHP used when building Pattern Lab #1060
Docs Add new docs about how to get started with automated testing using Jest. #1040
Implemented several housekeeping updates, improvements and fixes to our DevOps CI / CD process to continue to improve how smooth we ship Bolt releases. #1068
Major speed improvements to the build and deploy process (8 minutes faster!) + misc fixes and optimizations. #1038
Implemented a number of improvements and bug fixes related to the docs site and Pattern Lab UI #1050
Added a SCSS mixin named bolt-ie11-only
for writing CSS that only applies to IE11. #1055
Nightwatch test reporting + major improvements to Continuous Integration via the Github Checks API #1026
Setup multiple kinds of GitHub PR templates: bug, feature, release #1033
Upgrade + Streamline Release Process #1014
Decoupled the original SVG Icon build script from the icons themselves and moved to new home in @bolt/build-tools
. Added the ability to update the icon componentâs schema when icon assets are added / removed automatically + export list of available icons to a separate JSON file for better CMS integrations. #1020
Add persistent caching to twig namespace path discovery in Drupal #1086
Github Checks API: This sets up the GitHub Checks API for collecting information about a commit's build info. It removes the need to have Bolt Bot comment on PRs for deploy info and moves it to the "Checks" tab above and also allows more information to be shown over in that tab. #1025
<bolt-icon>
as expected. #1064items
to pinned_content
items
prop{% include "@bolt-components-band/band.twig" with {
content: content,
items: [
{
position: {
align: "end",
valign: "center",
row_start: 1,
column_start: 1,
column_end: 12,
},
content: pinned_share,
},
]
} only %}
pinned_content
prop{% include "@bolt-components-band/band.twig" with {
content: content,
pinned_content: {
upper: [
{
content: pinned_share,
align: "end",
},
],
}
} only %}
imageAttributes
, useAspectRatio
, width
, and height
propsimageAttributes
is now no longer required. Previously this had only been used internally inside the background image component.useAspectRatio
: use the new ratio
prop insteadheight
and width
props: the new ratio
prop now takes care of the previous need for these two props.Note: You can use this image as an reference to create some common layouts for testing.**
Published by sghoweri over 5 years ago
solid-star
icon to the Bolt icon library. #1002flex
-- allows the list component to now<bolt-list>
component to now be a fully baked web component #965 (see deprecation notes below to upgrade)<bolt-link>
component to now be fully client-side renderable as a standalone web component #963<bolt-link>
web component usage. #982<bolt-video>
component #955<bolt-video>
component to now allow for the "Share This Video" text be translated via a new optional config property #971<bolt-button>
component testing checklist items for both automated and manual testing #952<bolt-image>
and <bolt-video>
components to verify the <bolt-ratio>
dependency specified is getting pulled in and compiled as expected #939<bolt-figure>
to a fully client-side renderable web component; Twig figure
template now accepts table
and video
content, in addition to image
and icon
#989@bolt/components-critical-css
package for handling cross browser support for async CSS loading (via the <link rel="preload">
tag). #1039@bolt/build-tools
to automatically add Bolt component dependencies that are missing from the consumerâs .boltrc
config file #939.ts
, and .tsx
files in Bolt's local Webpack Build #964@bolt/core
click event handler util to allow toggling JavaScript methods that are on the window (vs only allowing methods that are on an element itself)@bolt/core
base component to no longer immediately trigger a component without any props to render (via the updated()
method call) -- fixes a minor issue discovered with the new Context API additions in #961 that can cause components using the new withContext
functionality to have undefined values initially until the component finishes rendering #964<bolt-code-snippet>
to ensure certain special characters like &, <, >
are escaped to render as expected #973<bolt-code-snippet>
component to apply escaping to all languages #985<bolt-table>
component's CSS fix to address a cross-browser theming bug with it's border color when compiled for production #977<bolt-list>
component's separator prop to work with dynamic display (ex. display="inline@small"
) #983<bolt-list>
component's inset
prop not rendering correctly #948<bolt-link>
lit-html templates causing unwanted whitespace; also removed line breaks from lit-html templates in renter-lit-html
's slot()
method #1005<bolt-button width="full">
does not appear to be full width when used inside of another web component's <slot>
#994Fixed broken image paths in the Bolt Card examples that test dynamically injected (personalized) behavior. #1051
Pattern Lab: Temporarily disabled our custom Pattern Lab PHP patch that automatically indents and removes extra white space in the HTML code preview shown in the Pattern Lab. We'll re-enable once a better PHP library is put in place that suffer from memory issues! #966
Vue.js Integration Added a workaround to the Vue.js example integration with Bolt -- fixes an issue with the Webpack build process not working as expected when running locally #972
Schemas: Fix schema syntax when multiple props are deprecated in a single component #988
Docs Site
now.sh
CLI library + config used for deploying Bolt updates to latest version; addresses deployment errors encountered + applies the latest security and maintenance updates from Zeit. #967v2.3.0
release candidate. #1035
incache
cache configâs max age + updates to skip cache behavior when deploying #1030@bolt/build-tools
to better handle any number of different ways the lang
config option can be set in a .boltrc
config file. #1029The original CSS classes for 3 Bolt utility classes involving z-index
and shadow
have been deprecated and renamed to be consistent with the naming convention globally used for all other utility classes. #946 -
These deprecated class names have been updated with the new syntax below and will be removed in the next major Bolt release, v3.0.0
.
Replace deprecated utility class names in these formats | With utility classes matching these formats |
---|---|
u-bolt-z-index--xx |
u-bolt-z-index-xx |
u-bolt-shadow--xx |
u-bolt-shadow-xx |
u-bolt-shadow--xx--hoverable |
u-bolt-shadow-xx-hoverable |
rounded
prop is now border-radius
The rounded
property for buttons is now deprecated and will be removed in a future major version of Bolt (Bolt v3.0).
Please use the new border_radius
property in Twig (or border-radius
in vanilla HTML) with a value of full
instead when needing round or pill shaped buttons. #987
image
and icon
props removed, media
prop addedThe image
and icon
props have been removed and a new property media
added. media
is an object that can contain an image
, icon
, video
, or table
. As the list of content types was growing, it made sense to group these options within a single property, media
.
There are no known instances of the figure
component in the wild at the moment, so we do not expect there to be any rework required to handle this schema change.
As part of the updates in #978, the original ordered and unordered list components have been updated and re-published to NPM under a new package name.
Because the original packages are still available on NPM at the previous v2.2.2
Bolt release, no immenent updates are mandatory, however we stongly recommend switching over to the new NPM packages to take full advantage of the major improvements now available.
To Upgrade:
package.json
file, remove any old references to @bolt/components-unordered-list
& @bolt./components-ordered-list
+ add the new @bolt/components-ul
and @bolt/components-ol
dependencies.boltrc
config, remove any old references to @bolt/components-unordered-list
or @bolt/components-ordered-list
and add the new @bolt/components-ul
and @bolt/components-ol
package namesOld Twig Template Path | Updated Twig Path |
---|---|
@bolt-components-unordered-list/unordered-list.twig |
@bolt-components-ul/ul.twig |
@bolt-components-ordered-list/ordered-list.twig |
@bolt-components-ol/ol.twig |
Published by sghoweri almost 6 years ago
This is a small hotfix release which updates the Bolt Core polyfill loader test to more specifically check for IE 11 in order to prevent the Shady DOM polyfill from loading unintentionally.
This addresses a performance hit in IE 11 with the initial Bolt v2.2.0 release.
Published by sghoweri almost 6 years ago
solid-star
icon to the Bolt icon library. #1002flex
-- allows the list component to now<bolt-list>
component to now be a fully baked web component #965 (see deprecation notes below to upgrade)<bolt-link>
component to now be fully client-side renderable as a standalone web component #963<bolt-video>
component #955<bolt-video>
component to now allow for the "Share This Video" text be translated via a new optional config property #971<bolt-button>
component testing checklist items for both automated and manual testing #952<bolt-image>
and <bolt-video>
components to verify the <bolt-ratio>
dependency specified is getting pulled in and compiled as expected #939<bolt-figure>
to a fully client-side renderable web component; Twig figure
template now accepts table
and video
content, in addition to image
and icon
#989<bolt-link>
web component usage. #982@bolt/build-tools
to automatically add Bolt component dependencies that are missing from the consumerâs .boltrc
config file #939.ts
, and .tsx
files in Bolt's local Webpack Build #964@bolt/core
click event handler util to allow toggling JavaScript methods that are on the window (vs only allowing methods that are on an element itself)@bolt/core
base component to no longer immediately trigger a component without any props to render (via the updated()
method call) -- fixes a minor issue discovered with the new Context API additions in #961 that can cause components using the new withContext
functionality to have undefined values initially until the component finishes rendering #964<bolt-list>
component's inset
prop not rendering correctly #948<bolt-code-snippet>
to ensure certain special characters like &, <, >
are escaped to render as expected #973<bolt-code-snippet>
component to apply escaping to all languages #985<bolt-table>
component's CSS fix to address a cross-browser theming bug with it's border color when compiled for production #977<bolt-list>
component's separator prop to work with dynamic display (ex. display="inline@small"
) #983<bolt-link>
lit-html templates causing unwanted whitespace; also removed line breaks from lit-html templates in renter-lit-html
's slot()
method #1005<bolt-button width="full">
does not appear to be full width when used inside of another web component's <slot>
#994now.sh
CLI library + config used for deploying Bolt updates to latest version; addresses deployment errors encountered + applies the latest security and maintenance updates from Zeit. #967The original CSS classes for 3 Bolt utility classes involving z-index
and shadow
have been deprecated and renamed to be consistent with the naming convention globally used for all other utility classes. #946 -
These deprecated class names have been updated with the new syntax below and will be removed in the next major Bolt release, v3.0.0
.
Replace deprecated utility class names in these formats | With utility classes matching these formats |
---|---|
u-bolt-z-index--xx |
u-bolt-z-index-xx |
u-bolt-shadow--xx |
u-bolt-shadow-xx |
u-bolt-shadow--xx--hoverable |
u-bolt-shadow-xx-hoverable |
rounded
prop is now border-radius
The rounded
property for buttons is now deprecated and will be removed in a future major version of Bolt (Bolt v3.0).
Please use the new border_radius
property in Twig (or border-radius
in vanilla HTML) with a value of full
instead when needing round or pill shaped buttons. #987
image
and icon
props removed, media
prop addedThe image
and icon
props have been removed and a new property media
added. media
is an object that can contain an image
, icon
, video
, or table
. As the list of content types was growing, it made sense to group these options within a single property, media
.
There are no known instances of the figure
component in the wild at the moment, so we do not expect there to be any rework required to handle this schema change.
As part of the updates in #978, the original ordered and unordered list components have been updated and re-published to NPM under a new package name.
Because the original packages are still available on NPM at the previous v2.2.2
Bolt release, no immenent updates are mandatory, however we stongly recommend switching over to the new NPM packages to take full advantage of the major improvements now available.
To Upgrade:
package.json
file, remove any old references to @bolt/components-unordered-list
& @bolt./components-ordered-list
+ add the new @bolt/components-ul
and @bolt/components-ol
dependencies.boltrc
config, remove any old references to @bolt/components-unordered-list
or @bolt/components-ordered-list
and add the new @bolt/components-ul
and @bolt/components-ol
package namesOld Twig Template Path | Updated Twig Path |
---|---|
@bolt-components-unordered-list/unordered-list.twig |
@bolt-components-ul/ul.twig |
@bolt-components-ordered-list/ordered-list.twig |
@bolt-components-ol/ol.twig |
Published by remydenton almost 6 years ago
This is a hotfix release. It includes one high priority fix:
Published by sghoweri almost 6 years ago
bolt-share
. #922<bolt-select>
custom element. #906@bolt/build-tools
to skip Bolt version check during non-prod builds #949@bolt/core updates
to help address cross-browser rendering inconsistencies by switching over from HyperHTML to Google's Lit-HTML library + updating existing components accordingly #951@bolt/core
: withContext
and defineContext
.
While not yet used by any components at the moment, these updates support several upcoming component enhancements (such as the in-progress work on the Card, Link, and List components) that involve contextual data and internal state management.
Check out this recent CSS Tricks article to learn more about the ideas behind this!
bolt-share
's tight spacing issue in FF. #922Three opacity-related utility classes are deprecated and will be removed in the next major Bolt release, v3.0.0
.
Replace them with the recommended classes shown in the table below or one of the other classes documented at https://feature-opacity-scale.boltdesignsystem.com/pattern-lab/?p=styleguide-opacity
Deprecated utility classes | Suggested replacement |
---|---|
.u-bolt-opacity-75 |
.u-bolt-opacity-80 |
.u-bolt-opacity-50 |
.u-bolt-opacity-60 |
.u-bolt-opacity-25 |
.u-bolt-opacity-20 |
Published by remydenton almost 6 years ago
This is a hotfix release. It includes one high priority fix:
Published by sghoweri almost 6 years ago
bolt-list
's display prop is used in conjunction with other props such as spacing and border. #921<bolt-list>
component to ensure the list item styling doesn't trickle down to any other nested <bolt-list>
s #917<bolt-button>
component's rendered
and ready
events not getting emitted as expected. #924Published by remydenton about 6 years ago
This is a hotfix release. It includes one priority fix found during QA of the last pega.com release. That release went ahead as planned, but this unblocks a "fast follow" update.
Published by remydenton about 6 years ago
This is a hotfix release. It includes one high priority fix discovered during integration: