Only render action models on the pages they apply to.
Review Request #14692 — Created Nov. 14, 2025 and updated — Latest diff uploaded
When rendering for models and views for actions were split up, we began
rendering the model JavaScript for every action on every page,
regardless ofapply_to. This caused some actions to fail to
instantiate on pages they weren't supposed to be on.This change restores a
should_render()call for model JavaScript,
ensuring we only get the actions appropriate for the page.
Unit tests pass.
Verified that JavaScript unit tests were no longer erroring out with
actions that couldn't instantiate.