Blazy 2.x API changes: theme_blazy() replaces sub-modules theme_ITEM() contents

Since 2.17 full release, on your permissions at /admin/help/blazy_ui under Use theme_blazy() option, theme_blazy() is now capable to replace sub-modules theme_ITEM() contents, e.g.: theme_slick_slide(), theme_splide_slide(), theme_mason_box(), etc.

HEADUPS:
Nothing will change at sub-modules' theme_ITEM() contents before or after you enable the option, unless you drastically Twig templates. In such a case, please disable the option till you have time to update your overrides.

At 3.x, we'll no longer ask for permissions, please be sure to test it out to spot the problems earlier, or migrate your overrides earlier.

Repeat, not replacing their established theme_ITEM(), just their contents when we all have dups with
IMAGE/MEDIA + CAPTIONS contructs. It is not a novel thing, see block.html.twig with its variants, etc.
Not a sudden course of actions, it was carefully planned since 2.x-RC1, 4 years ago from 2023, and never made it till 2.17.

If you see no difference, nothing to do. If any, be sure it is not caused by your non-updated overrides which should be updated prior to blazy:3.x. Only report if this is caused by blazy's mistake. Kindly provide markup comparison, or helpful screenshots, to spot the issues better.

Profits

:

• Tons of dups are reduced which is part of Blazy's job descriptions here.
• More cool kid features like hoverable effects, etc. will be easier to apply.
• When Blazy supports extra captions like File description, it will be available immediately to all once, rather than updating each modules to support it due their hard-coded natures.

Non-profits

:

• Overrides should be taken seriously from now on, or as always. Perhaps CSS overrides are the safest. Or at most a hook_theme_suggestions_alter().
• One blazy stupid mistake, including your override, kills em all. We'll work it out at Bugs reports if blazy's. It happens, and the world does not end yet.

Read more about blazy.api.php.