Summary

Only render action models on the pages they apply to.

Review Request #14692 — Created Nov. 14, 2025 and submitted Nov. 28, 2025, 9:50 p.m.

Information

Owner

chipx86

Repository

Review Board

Branch

release-7.1.x

Bugs

Depends On

Reviewers

Groups

reviewboard

People

Description

When rendering for models and views for actions were split up, we began
rendering the model JavaScript for every action on every page,
regardless of apply_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.

Testing Done

Unit tests pass.

Verified that JavaScript unit tests were no longer erroring out with
actions that couldn't instantiate.

Commits

Summary	ID
Only render action models on the pages they apply to. When rendering for models and views for actions were split up, we began rendering the model JavaScript for every action on every page, regardless of `apply_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.	62ecb2d3b5ebdce9db80f954a1075014bb67fcfc

Summary

Only render action models on the pages they apply to.

When rendering for models and views for actions were split up, we began rendering the model JavaScript for every action on every page, regardless of `apply_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.

62ecb2d3b5ebdce9db80f954a1075014bb67fcfc

flake8 passed.

JSHint passed.

Ship it!

```
Ship It!
```

Ship it!

```
Ship It!
```

Status:: Completed
Change Summary:: Pushed to release-7.1.x (d1c8347)