Tacsipacsi added a comment.
> 6. **_apisite.flagconfig()** > - Shows information about review flag configuration. > - API: https://www.mediawiki.org/wiki/Extension:FlaggedRevs#action=flagconfig I think this API endpoint should be deprecated: - It’s designed to contain much more data than what’s actually possible in 2025: it could report an arbitrary number of tags, but no more than one tag is possible anymore. It also reports `tier1` with a constant value of `1`, which isn’t useful. - It //doesn’t// include some very useful data, in particular the flaggable namespaces. https://hu.wikipedia.org/wiki/Szerkesztő:BinBot/huwiki/flaggedrevs.py (see T57081#8747890 <https://phabricator.wikimedia.org/T57081#8747890>) solves this by hardcoding the list of namespaces, which is clearly not scalable. - A minor issue is that it’s a separate module rather than a submodule of `query` – the latter would clearly indicate that it’s read-only, and it would allow bundling it with other requests (as far as I remember, Pywikibot also supports such bundling). For these reasons, I think `action=flagconfig` should be deprecated, and another module, say `action=query&meta=flaggedrevs` (or even `action=query&meta=siteinfo&siprop=flaggedrevs`) should be introduced, which returns at least the following data: - Whether the wiki is in protection mode (“English-style”) or not (“German-style”). Currently this is implicit from the fact that wikis in protection mode return zero tags, other wikis return one tag. - The name of the (only) tag; currently returned in `name` of the first tag if not in protection mode, but it would be needed in protection mode as well (it’s used as a parameter name when reviewing). - The maximum level of the (only) tag; currently returned in `levels` of the first tag if not in protection mode. It probably doesn’t make much sense to have more than one level in protection mode, but as far as I understand the code, it’s possible, so it would also make sense regardless of the protection mode setting. - Flagged namespaces, currently not returned at all. I already have some drafts for this, I just haven’t got to finish and upload them. If others agree, and so the module is about to be deprecated and completely reorganized, I’m not sure if it’s worth adding the old one to Pywikibot TASK DETAIL https://phabricator.wikimedia.org/T408726 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/
_______________________________________________ pywikibot-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected]
