Skip to content

Releases: Patternslib/Patterns

Release 8.0.3

23 May 15:49
Compare
Choose a tag to compare

8.0.3 (2022-05-23)

Bug Fixes

  • Build: Don't use index.js entry which should be used for module federation and would break chunk loading if used in a non-mf environment. (ad5381c)

Maintenance

  • Build: Support 2FA when releasing. (e8f02b4)
    Remove non interactive ci-mode from Makefile to allow for OTP prompt and two-factor auth on npm.
    Also remove dry-run as we now have to confirm each step anyways.

  • Build: Upgrade dependencies. (f2ac7ad)

  • Build: Use Underscore version 1.13.3 for module federation config. (403b9c8)

  • Be less verbose and use more debug log messages. (b05c03f)

  • pat modal: Update demo, re-activate autoload modal. (09d0e2b)

Release 8.0.2

19 May 11:34
Compare
Choose a tag to compare

8.0.2 (2022-05-19)

Bug Fixes

  • core base: Don't initialize a already initialized pattern. (d943de6)
    Improve the previous check by setting the var earlier.

  • core registry: Do not reinitialize and already initialized patterns registry. (809c119)

Release 8.0.1

18 May 16:42
Compare
Choose a tag to compare

8.0.1 (2022-05-18)

Maintenance

  • Bundle: Add the keyword "patternslib" to the npm package registry. (54fe5ba)

  • Bundle: Module Federation: Allow to pass the shared dependencies explicitly. When passed package.json dependencies are not automatically added. (7eba043)

  • Bundle: Upgrade dependencies. (d0a546b)

Release 8.0.0

17 May 15:42
Compare
Choose a tag to compare

8.0.0 (2022-05-17)

Features

  • Build: Dynamic Module Federation. Add config files and helpers. (7e7a2af)
    With module federation you can share dependencies over multiple bundles without
    loading them multiple times.

The dynamic part here allows the host to not know anything about it's remotes.
This concept can be used for add-ons to a base bundle.
Thanks @manfredsteyer for the help getting this to work!

Use the webpack/webpack.mf.js to extend your own webpack configuration with
dynamic module federation support.
In your main bundle (the "host") use webpack/dynamic_mf.js to configure the
entry point.

For more information see: docs/developer/module-federation.md.
For the general concept see: https://webpack.js.org/concepts/module-federation/

Co-authored-by: Johannes Raggam [email protected]
Co-authored-by: Manfred Steyer [email protected]

  • Build: Register jQuery globally without expose-loader. (dca0842)
    Remove the dependency on expose-loader and register jQuery globally in the
    globals.js module.

Import this module early to have jQuery registered for scripts which depend on
a global jQuery object.

This also fixes an additional request made by the expose-loader for
asynchronously loading jQuery.

  • core dom: dom.template engine. (61ca46f)
    Add a simple template engine in core.dom.template
    based on JavaScript template literals.

Maintenance

  • Build: Compatibility with Jest 28. (1795087)
    Don't transform preact.

  • Build: Compatibility with Jest 28. (69b7934)
    Remove jest-raw-loader dependency and add own loader based on keplersj/jest-raw-loader#239 for compatibility with Jest 28.

  • Build: Compatibility with Jest 28. (5679db0)
    Add jest-environment-jsdom as of jest 28 that isn't shipped anymore by default.

  • Build: Upgrade dependencies. (3260038)

  • Build: Upgrade fullcalender. (0b08573)

  • Build: Upgrade luxon to version 2. (5d12b9e)

  • Bundle: Upgrade jest to version 28. (4ac079f)

Breaking Changes

  • core registry: Use a global pattern registry. (737f3ed)
    Previously it was possible to use multiple pattern registries when multiple
    instances of the registry were used, e.g. in different bundles.

With this change we do use only one pattern registry storage which is
shared across instances of core.registry in multiple bundles.

This is a transparent change - the Patternslib registry API has not
changed at all. Just keep using registry.scan,
registry.register, etc.

But if necessary, there is a PATTERN_REGISTRY export in core.registry
which points to window.__patternslib_registry, a singleton in the global
namespace which is shared across instances of the registry.

Release 7.12.0

13 May 11:47
Compare
Choose a tag to compare

7.12.0 (2022-05-13)

Features

  • core dom: Add get_data and set_data methods to get or set data directly on DOM nodes. (1c21f05)

  • pat close-panel: New technical/internal pattern to close panels. (0c9231d)
    Add new pattern close-panel for internal use to close panels.
    This allows to initialize the close buttons after content injections.
    It also allows for nested panels where a later opened panel doesn't close a previous opened panel.

Bug Fixes

  • pat notification demo: Place close-button in each notification seperately. (2c57e3c)

Maintenance

  • Build: Supress console log messages in tests where HTMLFormElement.prototype.submit is not implemented. (a3bdc78)

  • Build: Upgrade dependencies. (22129ea)

  • pat calendar: Change console.log statement to a debug statement. (92a5999)

  • pat modal: Add numbers to test case names for easier starting individual cases. (62a38c9)

  • pat modal: Use new close-panel pattern for closing modals. (4a6029d)

  • pat notification: Code simplification and modernization. (f9d1492)

  • pat notification: Use new close-panel pattern for closing notifications. (b186066)

  • pat tooltip: Fix demo to use the referenced tooltip content. (6013b4b)

  • pat tooltip: Use new close-panel pattern for closing tooltips. (ca9fc9c)

Release 7.11.0

06 May 11:12
Compare
Choose a tag to compare

7.11.0 (2022-05-06)

Features

  • core events: Add mousedown and mouseup event factories. (62e1978)

  • core parser: Allow values to span multiple lines. Can be useful to nicely format bigger JSON values. (54a10c5)

Bug Fixes

  • pat auto suggest: Fix regression introduced in 7.0 where auto suggest wasn't able to handle pre-filled json items properly. (4c39332)

Maintenance

  • docs: Add note to Makefile about GITHUB_TOKEN in .env file. (2d10732)

Release 7.10.0

05 May 07:08
Compare
Choose a tag to compare

7.10.0 (2022-05-05)

Features

  • core utils: Add is_iso_date_time method to check for valid ISO 8601 date/time strings. (d9fcfac)

Bug Fixes

  • pat validation: Also validate date/time inputs when the value is empty. (39249b2)
    This clears eventual validation errors when the date input is cleared.

  • pat validation: Fix issue where Google Chrome would interpret an invalid date value like "ok-1" as a valid date. (0fb2359)

Release 7.9.0

28 Apr 21:00
Compare
Choose a tag to compare

7.9.0 (2022-04-28)

Features

  • pat push: Add support for desktop notifications. (009b7a9)

  • pat push: Added the option to append the fetched content at the end of the pat-push element (6e3c6dc), closes #876
    Fixes #876

  • pat push: Scan the injected element for patterns. (8c75fa1)

Release 7.8.0

15 Apr 10:26
Compare
Choose a tag to compare

7.8.0 (2022-04-15)

Features

  • pat tooltip: Initialize the tooltip's content after each refresh via get_content. This re-initializes any patterns after an update to the tooltip's contents. (665bea5)

Maintenance

  • Build: Remove customized main changelog template as due to conventional-changelog 4.3.0 the previous header's line break is preserved. (9e8ecbd)

  • Build: Upgrade dependencies. (9ea9c21)

  • pat tooltip: Use add_event_listener from core.events which better handles double registrations and makes it easier to unregister event handlers. (fe0f0d7)

Release 7.7.0

12 Apr 07:45
Compare
Choose a tag to compare

7.7.0 (2022-04-12)

Features

  • Introduce disable-patterns class to prevent from initializing. (5f137f0)
    To disable patterns when scanning markup for patterns, use the disable-patterns CSS class.

Previously we did use the dont-touch-this class.
This is deprecated due to a ambiguous name and will be removed in the next major version.

Bug Fixes

  • Build: Fix changelog template. (96f7bac)
    Since conventional-changelog 4.2.0 the previous header is merged to the
    end of the new changelog entry block.
    This is documented here: release-it/conventional-changelog#46
    As long as this issue is not resolved, we're adding a # at the end
    of the changelog block, intending the previous entry in the heading
    hierarchy, but that's better than a even more messed up changelog file.