thiemowmde added subscribers: hoo, aude, Addshore. thiemowmde added a comment.
I'm a Wikidata dev. What do you expect upstream to do? The wbeditentity API is, in essence, a fallback you can use when there is no specific API for a specific use case. There are several disadvantages in using wbeditentity, namely: - The edit summary will, in most cases, be an unspecific "the entity changed" because that's all the API module knows. Remember, the API module gets a big JSON blob of the full entity. Sure, in theory it's possible to create a diff and traverse it and create more specific summary lines if, for example, only a label changed. But that's (currently) not the job of wbeditentity. I would love to implement some magic that switches to more specific summary lines if possible, but even that will stop working if, for example, a label and a statement's value are changed in a single wbeditentity call. - Submitting a big JSON blob when, for example, only a label changed, wastes computational power and bandwith on all sides. I suggest to use wbsetlabel, wbsetdescription and wbsetaliases if only a single label, description or set of aliases (in one language) changed. I suggest to use wbsetsitelink if only a single sitelink changed. I suggest to use wbsetclaim if only a single statement changed. These are the most important, most relevant changes that result in the most bot-triggered summary lines. Switching to the more specific API modules would make these edits much, much more visible to all users. TASK DETAIL https://phabricator.wikimedia.org/T107712 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: thiemowmde Cc: Addshore, aude, hoo, Lydia_Pintscher, Ricordisamoa, pywikibot-bugs-list, jayvdb, thiemowmde, Aklapper, Ladsgroup, Malyacko, P.Copp _______________________________________________ pywikibot-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikibot-bugs
