Store Review UIs in a real registry.
Review Request #13536 — Created Feb. 12, 2024 and submitted
We had a kind of registry-like pattern for Review UIs, where we had
methods for registering and unregistering, and then stored them in a
list. This change adds a real registry for the backend storage.
Ran unit tests.
Summary | ID |
---|---|
edc0cb7b51fa20679df54bbe14d74f02f56f4271 |
Description | From | Last Updated |
---|---|---|
Missing docs with Version Added. |
chipx86 | |
Should be separated with a blank line (ideally, import would be at the top of the function). If we move … |
chipx86 | |
Should use Type for now, until we deprecate some older versions of Python. This is important because The type[...] actually … |
chipx86 | |
We could use an f-string here. |
chipx86 |
-
-
-
Should be separated with a blank line (ideally,
import
would be at the top of the function).If we move the registry import into
registry.py
, and forward that inreviewboard.reviews.ui
, there won't even be a need for this in-function import. We're a bit inconsistent today in our pattern here.This comment applies to all following imports.
-
Should use
Type
for now, until we deprecate some older versions of Python.This is important because The
type[...]
actually gets executed by Python, and will fail iftype
doesn't support generics. -