@matmarex, looks like you marked discussiontoolssubscribe API as internal. I just wanted to inquire as to the reason, and if we could get this turned into a regular API soon? This API could potentially be really useful to extensions, gadgets, and user scripts that would like to use it. Examples:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T294592 [EPIC] Ensure Talk Pages Project "Phase 1" work is easy to maintain, build upon, and learn from | |||
| Resolved | Esanders | T329474 Figure out why discussiontoolssubscribe API is marked as internal |
It was marked as internal because at the time, we weren't sure how topic subscriptions were going to be implemented in the end, and we didn't want to make any promises about the API stability.
I think it's stable now and it should be fine to use it elsewhere. We should unmark it as internal.
We should improve the validation and documentation while we're at it. For the page parameter, you're supposed to pass a title with a fragment pointing to the section, otherwise the subscription won't appear correctly on Special:TopicSubscriptions. And it's not obvious what the commentname should be (it's the ID value starting with h-).
Change 946553 had a related patch set uploaded (by Esanders; author: Esanders):
[mediawiki/extensions/DiscussionTools@master] Remove 'internal' flag from ApiDiscussionToolsSubscribe
Change 946553 merged by jenkins-bot:
[mediawiki/extensions/DiscussionTools@master] Remove 'internal' flag from ApiDiscussionToolsSubscribe/GetSubscriptions