Remove deprecation for passing non-string values to API add_field.
Review Request #14489 — Created June 28, 2025 and submitted
The API request
add_field
method has had a deprecation warning for a
while about passing in values that are not eitherstr
orbytes
. This
change replaces the warning+cast with an exception.There were a few places inside RBTools itself that were still hitting
this, all in the post implementation. These have been fixed up to format
the values as strings.
- Ran unit tests.
- Audited call sites to verify that we were passing string types
everywhere. - Posted changes, including ones that needed to upload binary files.
Summary | ID |
---|---|
7f16aed79145ff42fa8127f18108abd007bfd679 |
Description | From | Last Updated |
---|---|---|
We should prefix all strings with f when any in a multi-line string needs it. This avoids some warnings. What's … |
|
|
I feel like in the cases where we want to convert to a string, we should just cut out the … |
|
|
We should add a new version changed entry to say that only bytes and strings are accepted. |
![]() |
|
We can get rid of this. |
![]() |
-
-
We should prefix all strings with
f
when any in a multi-line string needs it. This avoids some warnings.What's the
type: ignore
for? -
I feel like in the cases where we want to convert to a string, we should just cut out the middle-man and use
str(...)
directly. This avoids the extra processing and results in the same thing.
- Commits:
-
Summary ID 9c67b0acd147822e9d888e45e2fc5f7be93187a7 dd4e668a91ea3a9f59ce3132c9b0c6b03984be46 - Diff:
-
Revision 2 (+56 -28)
Checks run (2 succeeded)
- Commits:
-
Summary ID dd4e668a91ea3a9f59ce3132c9b0c6b03984be46 e0522dd3779d3af6579b2490d7b3000f817b57a3 - Diff:
-
Revision 3 (+116 -46)
Checks run (2 succeeded)
- Commits:
-
Summary ID e0522dd3779d3af6579b2490d7b3000f817b57a3 7f16aed79145ff42fa8127f18108abd007bfd679 - Diff:
-
Revision 4 (+122 -46)