Name: [FIX] viin_brand_common, web_responsive, viin_brand_mail, to_backend_theme: keep brand CSS out of core test bundles

State: Killed

PR State: merged

PR Author: David Tran

PR Author Email:

PR: #673

Committer: David Tran

Committer Email: david.tran@tvtmarine.com

Commit: f8038c2c01bd0de302eae2017d09b5583e251c69

Description:

                                            [FIX] to_backend_theme: drop own SCSS from core's Hoot/QUnit bundles

Both web.assets_unit_tests_setup (core's Hoot test-setup bundle) and
web.tests_assets (the legacy QUnit bundle) carry
('include', 'web.assets_backend') and ('include', 'web.assets_backend_lazy'),
declared in Odoo core's own addons/web/__manifest__.py. That pulled
to_backend_theme's own backend-theme SCSS straight into core's own
unit-test pages, so several of core's own tests were measuring
to_backend_theme's styling instead of core's own defaults.

Add explicit ('remove', <path>) entries for all 7 of this module's
own SCSS files, spanning both source bundles
(web.assets_backend / web.assets_backend_lazy), to both TEST-ONLY
bundle keys in this module's own manifest. web.assets_backend and
web.assets_backend_lazy themselves (the real webclient) are untouched
- AssetPaths.remove() operates on the accumulated per-bundle path
list, not on the source bundle that contributed it. Confirmed both
statically (zero diff on either production bundle key) and live (the
two test bundles now resolve zero of this module's SCSS paths while
the production bundles still resolve all of them, unchanged, and both
test bundles still compile clean with zero errors).

Manifest-only change - this module has no test-page CSS shim to
remove.
                                            

Branch: 18.0

Age:

Up-time: Not finished