I have a few thoughts too:

Adding to our sprint board to take a look and offer code review support :)

MW-Interfaces-Team will take a look at this too see if there's an API specific solution, or if it's really at the storage layer.

Looks like Moderator-Tools-Team is on top of this. We are removing the MW-Interfaces-Team tag for now.

[Copied from: https://phabricator.wikimedia.org/T266454]
Just chiming in here (assuming that this is even still relevant) -- we assume that the own feature team (Moderator Tools, looks like) would be responsible for adding the required parameters. WE also assume that the generated docs will automatically update once that change is introduced.

Just chiming in here (assuming that this is even still relevant) -- we assume that the own feature team (Moderator Tools, looks like) would be responsible for adding the required parameters. WE also assume that the generated docs will automatically update once that change is introduced.

We just chatted about this in the MWI Triage. Based on some very early peeks through code, it seems like Wikifeeds does have an API spec defined, but it is not currently published/rendering anywhere. We will need to figure out a solution that works generally for allowing services outside of MW core to register specs for the REST sandbox.

Awesome. @Seddon confirmed that the apps team is good to go with internal testing whenever you are, and would like to get this rolling as soon as possible to avoid conflicts with other commitments this quarter. Let's plan on 1 week for each phase unless they report something here.

Adding a quick note based on conversations from the Hackathon and to answer Daniel's previous question -- the expectation here would be to include non-minified versions of SwaggerUI AND all dependent libraries. We are not considering this a blocker, and do not intend to move forward with that change. I'm going to mark this ticket as declined for now.

Also confirmed that my understanding is that all readinglist endpoints are all under v0, as they are all marked as 'unstable'.

@hnowlan -- just want to confirm that we will follow this rollout path, so that the mobile apps team has time to test and respond: