Make Pipeline settings generation reusable for consuming projects.
Review Request #11367 — Created Jan. 11, 2021 and submitted
We use a fairly custom Pipeline configuration for Djblets static media,
making use of wrappers for the LessCSS compiler and a standard set of
options and plugins for Babel and LessCSS. Consuming applications
(namely Review Board) use the same options, and have previously had to
duplicate the configuration. This meant that they didn't gain any
benefits from improvements made to this configuration.
This change introduces a new
build_pipeline_settings()function that builds a standard
PIPELINEsettings dictionary. It provides the standard settings we
use, but allows a degree of customization. Consumers can make use of
this directly, or modify the generated settings after the fact.
Built a Djblets package successfully.
Unit tests pass.
Made use of this in Review Board and verified the resulting static media.
Updated to use the proper path to babel for Djblets 2.x (this change was originally on master).
Revision 2 (+330 -56)
Checks run (2 succeeded)