-
-
-
-
-
-
-
-
-
-
-
-
libpurple/tests/test_request_field.c (Diff revision 1) Once the int validation strings are marked for translation, we'll need to add an environment to this test to set
LANG=C
.I tried finding a way to do this at run time, but google wasn't coming up with anything. It might be as easy as just a
g_setenv
before initializing gettext, but actually maybe we don't need to do any of this because our tests don't initialize gettext?
Add a PurpleRequestField:valid property and is_valid vfunc
Review Request #2346 — Created March 14, 2023 and submitted
- Add a
PurpleRequestField:valid
property andis_valid
vfunc. - Add a
GDestroyNotify
parameter for the validator data, and document the callback. - Correct the property notification in
purple_request_field_bool_set_value
.
Compiled and ran
ninja test
Summary | ID |
---|---|
705089d4ed02d786325f783e0f4a45fa4e6ed64f |
Description | From | Last Updated |
---|---|---|
%NULL |
grim | |
%NULL |
grim | |
should we be freezing here? |
grim | |
mark for translation |
grim | |
Should we be freezing here? |
grim | |
freeze notify? |
grim | |
freeze notify? |
grim | |
should be marked for translation |
grim | |
should be marked for translation |
grim | |
freeze? |
grim | |
Once the int validation strings are marked for translation, we'll need to add an environment to this test to set … |
grim |
Change Summary:
Add freezes, translation, and
%
.
Commits: |
|
|||||||
---|---|---|---|---|---|---|---|---|
Diff: |
Revision 2 (+478 -70) |