I want to validate an assumption about overriding a single JS file chunk from plone.staticresources
, based on things I've pieced together from a few different threads here — maybe someone has either done this already, or knows if I'm playing with fire here (e.g. filename instability).
To avoid maintaining a private fork of plone.staticresources
:
-
I want to consider deploying a customization of the pat-tinymce link modal in an add-on as a single resource file override (via
zc3.jbot >= 1.1.0
resource override) -
with the single resource here (
plone.staticresources
master branch) beingstatic/bundle-plone/chunks/tinymce_plugins.6f290aa6d2213b2ee16d.min.js
having its equivalent chunk asset (different filename, but easy enough to see in viagit status
after build) to anoverrides/resources
directory in my policy product with a filename ofplone.staticresources.static.bundle-plone.chunks.tinymce_plugins.6f290aa6d2213b2ee16d.min.js
(well, this and probably the chunk containing related CSS embedded in JavaScript).
I have already built my changes against mockup and its usual webpack processes, and I'm satisfied with what I have put together, but want a reasonable way to narrowly package just my cutomization/override into my policy package.
Is this reasonable? Are there any other pitfalls I might encounter besides moving target of chunk/resource filename between Plone releases?