v3.5.0

What's Changed

Added

• datalayer feature (#160) — one thin dataLayer layer to replace the site-local custom_datalayer copies. Off by default behind the datalayer flag in drupal_kit.feature_flags; its settings live in the new drupal_kit.datalayer config object. With the flag on and every setting at its default it sends one thing, generate_lead after a webform submission, by the redirect (?token=) and by the AJAX confirmation alike. status_codes, page_context and click_events add the rest, each off until switched on. lead_form_data (all, none, keys) decides which submitted values the lead carries. A project adds its own pushes by subscribing to DataLayerEvents::COLLECT and changes a lead through DataLayerEvents::LEAD, which also carries the submission and, like COLLECT, a cacheability() for what the push depends on. Inline scripts are encoded with JSON_HEX_*. While a module named custom_datalayer is installed the layer sends nothing and the status report says so. drupal_kit_post_update_feature_flag_datalayer() declares the flag and the settings on a site that already has the module. drupal/webform becomes a dev dependency and a suggestion; the module works without it.

Pull Requests

• #161 — feat(datalayer): thin dataLayer layer behind the datalayer flag (#160)

Full Changelog: v3.4.0...v3.5.0