The backend already sends the default to the client.
The client should accept the 'default' field, and if that's omitted IMHO a safer default is '' (empty string, group has no effect).
Description
Description
Details
Details
| Project | Branch | Lines +/- | Subject | |
|---|---|---|---|---|
| mediawiki/core | master | +18 -21 | RC Filters: correctly read default value for 'string_options' filters |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • DannyH | T171977 Annual Plan 2017-2018, Audiences 5: Increase current editor retention and engagement | |||
| Resolved | • DannyH | T171981 Annual Plan 2017-2018, Audiences 5, Goal 2: Give better ways to monitor contributions | |||
| Resolved | • jmatazzoni | T157642 Graduate New Filters UX out of beta on Recent Changes on ALL wikis | |||
| Resolved | • jmatazzoni | T144458 Launch ERI RC page features as a Beta Feature to all wikis | |||
| Resolved | Mooeypoo | T144448 Build all front-end elements for the new Recent Changes (RC) Page user interface | |||
| Resolved | SBisson | T160092 Client should handle default for 'string_options' groups |
Event Timeline
Comment Actions
Change 345444 had a related patch set uploaded (by Sbisson):
[mediawiki/core@master] RC Fitlers: correctly read default value for 'string_options' filters
Comment Actions
Change 345444 merged by jenkins-bot:
[mediawiki/core@master] RC Filters: correctly read default value for 'string_options' filters
Comment Actions
Checked as a part of regression testing on betalabs - all functionality seems to be in place.