Yay! Thanks, @hashar and @Jdforrester-WMF!

Thanks, @hashar! This all looks great.

🎉 Thanks, @Ameisenigel!

Looks like Api-User-Agent headers are now accepted by both the API Gateway and MediaWiki REST API. Thanks, Petr!

Fixed by https://gerrit.wikimedia.org/r/c/mediawiki/core/+/693508

Declining this task since we'll be looking into creating an API sandbox alongside improvements to the API reference docs

Declining this task since there's an open patch to add support for Api-User-Agent headers in the Core REST API (https://gerrit.wikimedia.org/r/c/mediawiki/core/+/693508)

Will be fixed by https://gerrit.wikimedia.org/r/c/mediawiki/core/+/693508

Just wanted to drop by and say that https://www.mediawiki.org/wiki/Cli is looking great! I'm happy to help review when you get to that stage.

Thanks for sharing this feedback, all! For some general context, the Architecture Team has posted the knowledge store data model on wiki. We’re planning to take this data model through the technical decision-making process, but for any additional feedback in the meantime, feel free to post to the talk page there.

@Lucas_Werkmeister_WMDE I'd love to get your feedback on what you think would be the best style for these JavaScript examples. Would you prefer something simpler like the shorter example in the task description?

Hi @Lucas_Werkmeister_WMDE, great points. Looks like we need two additional tasks here: one to allow Api-User-Agent in the MediaWiki REST API requests and one to fix the examples in mw:API:REST API/Reference in the short term. I'll go ahead and open those. Thanks for doing these tests and writing this up!

Looks good, @RBrounley_WMF! Unfortunately, schema.org doesn't have project as a property of Article, so we're using isPartOf for the wiki:

Switching tags to the correct API for this endpoint

Updated the main Season of Docs page for 2021 and created https://www.mediawiki.org/wiki/Season_of_Docs/Past_projects. The remaining redlinks on https://www.mediawiki.org/wiki/Season_of_Docs/Administrators are intentional since they are meant to act as a way to create pages for a new year's program.

No, I'm not able to reproduce, so assuming fixed for now

Thanks for your responses, @kostajh! I've add the POST endpoint to the docs. If there's anything incorrect, feel free to edit. If everything looks good to you, I think this task can be resolved. (I deleted the redirect page; no worries! I should figure out a way to make the sidebar less picky...)

Thanks for creating the wiki pages, @kostajh! I've reviewed and made a few edits. The docs are now at https://api.wikimedia.org/wiki/API_reference/Service/Link_recommendation (I've opened a patch to fix the link in the swagger spec.)

Thanks, @kostajh! I'll take a look today

Sounds good to me. Thanks, @kostajh!

I'm ok with keeping the rendered swagger docs. (It wasn't my intention to imply that they should be removed.) Especially since we're getting them essentially for free, I don't see a reason to remove them. The only thing I'd recommend is that, if we don't want people to access the API via addlink-simple.toolforge.org, we add a note about that to the swagger docs.

Actually, yes that would be great if you have time. I could help with editing after a first pass. If you don't have time that's OK as well, I can get to it later this week or next week.

Sure thing! I'll start as soon as the 504 clears up.

I'll have a go at adding the docs.

Sounds good! I'm happy to step in and add the docs if needed, just let me know. This doc has some info that should be helpful.

Hi @kostajh, Thanks for opening this task!

Hi @Ejegg, it seems like the patch didn't end up going out. Is there anything I can do to help?

Product management has decided to hold off on publishing this blog post in its current form. Thanks for all your help, @srodlund!

Stalled pending product management update

Thanks, Legoktm!

All tests are now passing 🎉

Thanks! This is no longer blocked by technical issues, but I'm leaving this as stalled pending management review

Awesome! Thank you!

GSoD 2020 is complete!

GSoD 2020 is complete!

GSoD 2020 is complete!

GSoD 2020 is complete!

GSoD 2020 is complete!

GSoD 2020 is complete!

GSoD 2020 is complete!

Config patch was merged, and I've verified that beta still works as expected. As a note for future changes to the beta config, even beta-only changes should follow the deploy process to avoid leaving undeployed commits for the next person.

Thanks, @hashar! This is good to know. So is it ok to ignore the post-merge build failure? Looking at the output, it seems to be failing on "Cannot open file "/workspace/src/extensions/WikimediaApiPortalOAuth/tests/phpunit.php".

Verified on beta

Unblocked pending deployment on Feb. 3

Verified on beta. Thanks, Bill!

2. If the app makes calls to both api.wikimedia.org and MediaWiki action endpoints, does this mean we have to register a key in both places, and does that mean a change for the login web flow? Or do we wait for all data-modifying APIs that we call via MediaWiki to be implemented in api.wikipedia.org so that we just have a single API key?

Verified on beta

Hi Clinic Duty friends, would it be possible for you to take a look at this? This issue is currently blocking the API Portal.

Hi @srodlund, thanks for your edits! Unfortunately, this is blocked again, and we won't be able to post next week. I don't have a new target date, hopefully sometime in February, but I'll let you know when I know more. Setting this to Stalled for now

Blocked by T272665

With T269880 resolved this is now unblocked

Verified in production. Thank you!