We can just create action=watch. If people want to edit and watch/unwatch a page at the same time, they'll have to make two requests.

(In reply to comment #1)

We can just create action=watch. If people want to edit and watch/unwatch a
page at the same time, they'll have to make two requests.

Would the settings defined in the inwiki preferences then apply to edits? the settings for watch creation, watch edits, watch moves and watch deletes.

I have at the moment a real problem with this in Twinkle, that I don't know if the specified value in wpWatchThis is based on a per user earlier specified for this page, or if it's the default. Some actions would preferably work like this: if the user in the script config has specified to watch the page, then we will watch the page, else if not, if the page has been already watched by the user, then we keep watching the page, if only the default says we should watch the page, we won't watch the page. At the moment, I can only see two of those, and it's a problem.

(In reply to comment #2)

(In reply to comment #1)
Would the settings defined in the inwiki preferences then apply to edits? the
settings for watch creation, watch edits, watch moves and watch deletes.

Good point there. Maybe action=edit should have an epWatch parameter (set to either 0 or 1) that overrules everything. If epWatch isn't set, default behavior would be observed (i.e. watch if the prefs say so, else don't change the watch flag). If you want this done, though, contact the maintainer of the APIedit_vodafone branch.

Implemented with watch and unwatch parameters in r31514