Djblets 1.0.11 Release Notes¶
Release date: March 19, 2019
Less 3.9 is now used to build all stylesheets.
This provides a number of new capabilities for our stylesheets, including referencing variables within mixins, maps, and many other improvements.
Added a fallback for when other avatar services cannot be used.
When no other avatar service is available, a fallback service is automatically used that displays the first two letters of the username on top of a background color generated based on a hash of the username.
This ensures that there’s always something to display, even if the user or administrator has opted out of all other forms of avatar services.
Reworked the CSS class names and styles for existing config forms components.
We’ve begun work on moving to a clearer, documented set of CSS classes for our config forms widgets that provide a better naming structure and defaults for styles that can be more easily built upon. These are not fully solidified today, and may change in future releases.
These are not used currently by the rest of the config forms code, but can be used by custom templates and widgets, giving them a head start for a complete switch-over intended for Djblets 2.0.
djblets-l-config-forms-containerCSS class for container elements.
This can (and, going forward, should) be used to group sections of content in a config form. It provides margins between the container and other components, and offers modifier CSS classes to make the top or bottom sides flush (using
-is-bottom-flushCSS classes, respectively) or to recess within the parent container (using
Parts of the styling may change in future releases.
Added CSS classes and styles for lists and list items.
List items can now have a state associated with them, which adds a colored border to the left-hand side of the item. By default,
-is-disabledCSS classes can be applied to each least item, setting an appropriate border. Additional styles can be defined in Less using the
List items can also make use of
-has-actionsCSS classes, which control padding on the left-hand side of the item and right-hand side of the item, respectively. As shorthand, these can be applied to all items by using
-all-items-have-actionsCSS classes on the list itself.
Added a new UI for adding and listing integration configurations.
This provides a complete revamp of the UI for working with integrations. The list of configured integrations is now presented as a standard list, showing the integration type, configuration name, enabled/disabled state, and a button for removing the integration.
Adding a new integration is done by clicking Add Integration, which will display a pop-up list of all available integrations.
This new UI makes it easier to work with large numbers of integrations and configurations, and is more easily expandable in the future to offer an improved interface for browsing available integrations.
Added embedding of the integration list and configuration pages outside of the Django administration UI.
Consumers can define subclasses of
BaseIntegrationConfigFormViewto display the list of integrations in any page. Alternatively, for the list, they can make use of the view mixin,
IntegrationListContextViewMixin, to provide the state needed for rendering the page.
The URLs for these views can then be generated using
build_integration_urlpatterns(). This allows the view subclasses to be specified and a URL namespace to be defined for that usage. If a namespace is used, then subclasses must override
get_edit_config_url()on the list view subclass in order to specify the right URLs.
These pages need to use the
- Christian Hammond
- David Trowbridge