https://bugzilla.wikimedia.org/show_bug.cgi?id=38843
jeb...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeb...@gmail.com
--- Comment #3 from jeb...@gmail.com 2012-08-07 09:50:57 UTC ---
The wbsetitem was initially an module for development support only, but has
since been the module preferred by the some of the bot programmers. As such
there is one mode of operation that is important; set those fields from the
item that are specified and leave the rest of the fields unchanged.
The primary use case is to add or remove a number sitelinks and leave the rest
as they are. To replace the whole list with a new one will make it necessary to
do an additional query, and also introduce a race condition.
To make the operation as similar as possible an set operation was used for
aliases, that is also motivated by what was simplest to implement, but should
operate on an add/remove -basis and not replacing the whole list. Labels and
descriptions should replace whats presently set, including remove the value.
Sitelinks should be set and removed.
A solution might be to give the new values as "operational objects" that carry
an operation and additional parameters. This makes it possible to specify if a
value should be replaced, set, added or removed - or something completely else.
I wonder if there are some kind of more generic modules that are so alien to
the core project scope that they really should be created and maintained
outside the project, perhaps as separate extensions. For example get-modules
more in line with the ordinary query-modules, and probably also set-modules
with more iterator-like behavior.
--
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
