Port RB.MenuButtonView to TypeScript and spina, remove SplitButtonView.
Review Request #12824 — Created Feb. 3, 2023 and submitted
This change ports the MenuButtonView UI element over to our new
TypeScript/spina framework.The
MenuButtonView
had mostly replaced the oldSplitButtonView
,
which had been marked as deprecated since 4.0 (and which had become a
simple wrapper). As part of this change, I've moved the couple old uses
of SplitButtonView over to use MenuButtonView directly.
- Verified "Publish" button functionality on the review dialog and draft
review banner. - Ran js-tests.
Summary | ID |
---|---|
ed1a24257f057c3a4b40644f083400253fd51ab9 |
Description | From | Last Updated |
---|---|---|
Can we make sure we're using one-line summaries for these? These will all eventually go through the same Napoleon doc … |
chipx86 | |
One-line/sentence summary here too. And below. |
chipx86 | |
Blank line between these. Makes it easier to document the instance variables when public. And actually, we should probably stick … |
chipx86 | |
Wonder if we should start making these static. I can't remember if there are currently any issues using that. |
chipx86 | |
I don't think we need to call the parent when subclassing BaseView/View. |
chipx86 | |
No need to call the parent here. It's explicitly empty. |
chipx86 | |
We should use ... as Element instead of <Element>.... This is the recommended syntax in TypeScript going forward (designed to … |
chipx86 | |
Can we sort this? |
chipx86 | |
This shouldn't be indented. |
chipx86 | |
We should also include Version Added here. |
chipx86 | |
We can use the _ template literal stuff for these gettext calls. (_ makes ESLint grumble a bit, but I … |
chipx86 | |
Leftover debugging. |
chipx86 | |
Leftover debugging. |
chipx86 | |
Can we put this in alphabetical order? |
chipx86 | |
These should be combined, updated for bullet points. |
chipx86 |
-
-
Can we make sure we're using one-line summaries for these? These will all eventually go through the same Napoleon doc handling that the Python code goes through, so it'll need to conform to that.
-
-
Blank line between these. Makes it easier to document the instance variables when public.
And actually, we should probably stick to the usual ordering of public and then private.
-
Wonder if we should start making these static. I can't remember if there are currently any issues using that.
-
-
-
We should use
... as Element
instead of<Element>...
. This is the recommended syntax in TypeScript going forward (designed to avoid issues with JSX).Here and anywhere else we may be doing it.
-
-
-
-
We can use the
_
template literal stuff for thesegettext
calls.(
_
makes ESLint grumble a bit, but I plan to address that.) -
-
- Commits:
-
Summary ID 69595a56dc02ac599b9afa939771c491d48a2542 ed1a24257f057c3a4b40644f083400253fd51ab9 - Diff:
-
Revision 2 (+514 -580)