
david got a fish trophy!

Add new resources, part 2/7.
Review Request #14341 — Created Feb. 10, 2025 and updated
This change adds the following new resource implementations:
- ChangeItemResource
- ChangeListResource
- DiffContextResource
- LastUpdateResource
- ReviewRequestDraftResource
- StatusUpdateItemResource
- StatusUpdateListResource
- Ran unit tests.
- Used the new resources from a test script and saw that everything
worked as expected.
Summary | ID |
---|---|
6e0ee6adeb52a440e4587d34c03874c665daed4f |
Description | From | Last Updated |
---|---|---|
Something that occurred to me while reviewing this. Since we have some deprecated functions and some new ones, we might … |
|
|
line too long (80 > 79 characters) Column: 80 Error code: E501 |
![]() |
|
This isn't needed in the TypedDict. |
|
|
Can we link this here and below? We can use standard Sphinx references, since we reference RB docs. |
|
|
The API doesn't allow for mutating this, so we should make this a Mapping. |
|
|
This is in a TypedDict, so we don't need this here. |
|
|
These are all Mapping now. |
|
|
Small nit, but can we list these as bullet points? |
|
|
Can we separate these out into paragraph per, so it doesn't all run together? Alternatively, worth having an enum? This … |
|
|
Should we mark this deprecated then? Even if we're going to keep it around for backwards-compatibility. |
|
|
Same question as above. |
|
|
And here. And others that are considered legacy. |
|
- Commits:
-
Summary ID 6f5602a17810328abd46baddf518db01559a6bea 728914f6dedfac55afb384a5ad57b3561bfa2ade - Diff:
-
Revision 2 (+2368 -136)
Checks run (2 succeeded)
- Commits:
-
Summary ID 728914f6dedfac55afb384a5ad57b3561bfa2ade b4920d5c38f97eaf38c9760cc881c9b3ff89822d - Diff:
-
Revision 3 (+2376 -140)
Checks run (2 succeeded)
-
-
Something that occurred to me while reviewing this. Since we have some deprecated functions and some new ones, we might want to include for every function a Review Board compatibility range of some sort. This absolutely doesn't need to be part of this change, but it's probably worth having, especially as we introduce new APIs.
-
-
-
-
-
-
-
Can we separate these out into paragraph per, so it doesn't all run together?
Alternatively, worth having an enum? This question more broadly applies to other
Literal
instances. Purely food for thought, and nothing that would need to go into this set of changes. -
Should we mark this deprecated then? Even if we're going to keep it around for backwards-compatibility.
-
-
- Commits:
-
Summary ID b4920d5c38f97eaf38c9760cc881c9b3ff89822d 6e0ee6adeb52a440e4587d34c03874c665daed4f - Diff:
-
Revision 4 (+2384 -140)