UI Elements Changelog BETA

Subscribe to this page via RSS


1.3.0Time zone option for Availability Viewer

minor August 16, 2019

An optional tzid parameter that allows the Availability Viewer to be initialised with a specific time zone. If tzid is declared, the time zone will be displayed in the footer of the Element.

Note: using this new tzid option will cause the Availability Viewer to render in a timezone that may not match the timezone of the user’s computer. Be sure to highlight this to the user.

1.2.5Week-rounding logic

patch August 14, 2019
Fixes a bug where available periods starting on a Sunday were causing the Availability Viewer to display the preceding week (with no availability) on load.

1.2.3Smarter overrun calculation handles cross-dateline days

patch July 25, 2019

Slots that ‘overrun’ the end of the visible period are found using a moment.diff() between the end of the period and the end of the slot.

This method failed to account for days that crossed the dateline. It now does.

1.2.2Slot heights

patch July 23, 2019

Slot heights were far too high for the interval: 15; duration: 30 combo.

Now, an hour will always be 60px high, and the slots will be divided accordingly.

1.2.0callback for rules

minor July 22, 2019
  • triggered on successful ‘rules saved’ response from API

1.1.2sniffing timezone for mock data

patch July 18, 2019

1.1.1Reload

patch July 18, 2019
  • More specific docs links in errors/warnings when parsing options.

  • Storing original options ‘immutably’ so we can re-parse when update() method is called.

1.1.0Time Zone Translation

minor July 4, 2019
  • time zone display in Availability Rules footer

  • translations moved into json

  • time zone translation handler

1.0.0UI Elements v1.0.0

major June 26, 2019

The release of UI Elements v1.0.0 marks an important transition from prototype to full-fledged product. We have been able to shape the Elements into a robust suite suitable for use in any application environment.

The changes from v0 to v1 are designed to enable a more flexible and customizable set of Elements, as well as providing a solid platform for future expansion. The new config option standardizes many of the more ad-hoc options from early versions, and all style-related options have been moved to the styles option. The callback format has also been amended to support multiple notification types from a single Element, paving the way for richer and deeper integrations.

Find out more in the Upgrade Guide, including the upgrade steps for those using older versions.

Search