Summary

Split the rendering of JavaScript action models and views.

Review Request #14665 — Created Oct. 31, 2025 and updated Nov. 8, 2025, 11:30 a.m.

Information

Owner

chipx86

Repository

Review Board

Branch

release-7.1.x

Bugs

Depends On

Reviewers

Groups

reviewboard

People

Description

We now have enough support for multiple views for the same action. It's
time to separate out the registration of the models and the views so
there's no longer a one-to-one association.

The new BaseAction.render_model_js() is responsible for writing the
JavaScript to render an action model. Every registered action in Python
will be registered in JavaScript.

The existing BaseAction.render_js() (old name currently kept for
compatibility reasons) will render the view. This is now only called
when the attachment points used on the page, rather than all attachment
points. That's handled in the {% actions_html %} template tag.

The template tag renders the HTML for the attachment point where the
template tag is placed, and then sets up a page injection containing the
JavaScript views. Then, when rendering the JavaScript models, the
injected JavaScript views content will be included.

Some of the design of this change is here to facilitate the upcoming
improvements to attachment points.

Testing Done

Unit tests pass.

Tested that all the actions on the page displayed and worked correctly.

Commits

Summary	ID
Split the rendering of JavaScript action models and views. We now have enough support for multiple views for the same action. It's time to separate out the registration of the models and the views so there's no longer a one-to-one association. The new `BaseAction.render_model_js()` is responsible for writing the JavaScript to render an action model. Every registered action in Python will be registered in JavaScript. The existing `BaseAction.render_js()` (old name currently kept for compatibility reasons) will render the view. This is now only called when the attachment points used on the page, rather than all attachment points. That's handled in the `{% actions_html %}` template tag. The template tag renders the HTML for the attachment point where the template tag is placed, and then sets up a page injection containing the JavaScript views. Then, when rendering the JavaScript models, the injected JavaScript views content will be included. Some of the design of this change is here to facilitate the upcoming improvements to attachment points.	ac05257d3e82428a725f410c1bcd8cc5f9766b95

Summary

Split the rendering of JavaScript action models and views.

We now have enough support for multiple views for the same action. It's time to separate out the registration of the models and the views so there's no longer a one-to-one association. The new `BaseAction.render_model_js()` is responsible for writing the JavaScript to render an action model. Every registered action in Python will be registered in JavaScript. The existing `BaseAction.render_js()` (old name currently kept for compatibility reasons) will render the view. This is now only called when the attachment points used on the page, rather than all attachment points. That's handled in the `{% actions_html %}` template tag. The template tag renders the HTML for the attachment point where the template tag is placed, and then sets up a page injection containing the JavaScript views. Then, when rendering the JavaScript models, the injected JavaScript views content will be included. Some of the design of this change is here to facilitate the upcoming improvements to attachment points.

ac05257d3e82428a725f410c1bcd8cc5f9766b95

Issues

Description	From	Last Updated
Might as well specify "action's Javascript model" here.	maubin	Nov. 4, 2025, 8:18 p.m.
We should be more specific here and say "... for action model".	maubin	Nov. 4, 2025, 8:18 p.m.
The part about setting up the model should be removed from the sentence now.	maubin	Nov. 4, 2025, 8:18 p.m.
It's a little bit confusing that we assign actions twice and iterate over for action in actions twice. Can we …	david	Nov. 8, 2025, 11:30 a.m.
Expected a string and instead saw %. Column: 2 Error code: W095	reviewbot	Oct. 31, 2025, 2:26 a.m.
Expected ':' and instead saw 'load'. Column: 4 Error code: E021	reviewbot	Oct. 31, 2025, 2:26 a.m.
Expected a JSON value. Column: 9 Error code: E003	reviewbot	Oct. 31, 2025, 2:26 a.m.
Expected '}' and instead saw 'actions'. Column: 9 Error code: E021	reviewbot	Oct. 31, 2025, 2:26 a.m.
Unrecoverable syntax error. (11% scanned). Column: 9 Error code: E041	reviewbot	Oct. 31, 2025, 2:26 a.m.
Same comment as the one on /r/14663, should we \|escapejs this?	maubin	Nov. 4, 2025, 8:18 p.m.

flake8 passed.

JSHint failed.

JSHint

reviewboard/templates/actions/action_view.js (Diff revision 1)
The issue has been dropped. Show all issues
```
Expected a string and instead saw %.

Column: 2
Error code: W095
```
reviewboard/templates/actions/action_view.js (Diff revision 1)
The issue has been dropped. Show all issues
```
Expected ':' and instead saw 'load'.

Column: 4
Error code: E021
```
reviewboard/templates/actions/action_view.js (Diff revision 1)
The issue has been dropped. Show all issues
```
Expected a JSON value.

Column: 9
Error code: E003
```
reviewboard/templates/actions/action_view.js (Diff revision 1)
The issue has been dropped. Show all issues
```
Expected '}' and instead saw 'actions'.

Column: 9
Error code: E021
```
reviewboard/templates/actions/action_view.js (Diff revision 1)
The issue has been dropped. Show all issues
```
Unrecoverable syntax error. (11% scanned).

Column: 9
Error code: E041
```

Fix it!

reviewboard/actions/base.py (Diff revision 1)
An issue was opened. Show all issues
```
Might as well specify "action's Javascript model" here.
```
reviewboard/actions/base.py (Diff revision 1)
An issue was opened. Show all issues
```
We should be more specific here and say "... for action model".
```

reviewboard/actions/base.py (Diff revision 1)

An issue was opened. Show all issues

The part about setting up the model should be removed from the sentence now.

reviewboard/templates/actions/action_view.js (Diff revision 1)
An issue was opened. Show all issues
```
Same comment as the one on /r/14663, should we |escapejs this?
```

Fix it!

reviewboard/actions/templatetags/actions.py (Diff revision 1)

An issue was opened. Show all issues

It's a little bit confusing that we assign actions twice and iterate over for action in actions twice.

Can we either just move the get_for_attachment calls into the for lines, or have two different variable names (like toplevel_actions and actions_with_children?)