To provide some context, until recently, the API was in bad shape. Basically, the first time we wrote an application we'd maybe write some application.whatever methods, which shared some code with the rest of the application but not all of it, and then the API and application wouldn't always get changed in the same way. This resulted in methods like repository.create which can do maybe 20% of what the web UI can, does it in different, inconsistent ways, and edits made by the API might look or work differently than web UI edits. In bad cases, they'd even do different policy/permissions checks. This caused many many problems for a very long time.

Thanks a lot for putting your time into replying to my comments. I am thinking squarely in the context of T6027, and was looking primarily at the bullet points here as a stepping stone towards that. i.e.

Changes like T10569 should probably happen first. This is likely to be very complex, and is probably not a good task for a new contributor.

Are workboards 'un-beta' now, and stable enough for it to be worth putting some work into this? I can't promise to have time, but I'm certainly interested in having a look at this.

T10599 asks for column move APIs, which are adjacent to this.

How can i use DiffusionBrowseController.php to brow my files with non-latin character names correctly?

okay - I'll just fix this

Sorry to necro an old thread, but I, too, am looking for information about this particular API method.

Please see Planning. We update tasks when new information is available, we don't have a secret shadow tracker with lots of juicy secrets that we aren't sharing.

Any update here? As far as I can tell it's also impossible to use any of the differential API endpoints using OAuth .

After D15105:

Thank you very much! You solved all my problems :D

I believe this is fixed at head. Let us know if you're still seeing issues.

(And there are no configuration settings you can change which will possibly impact or resolve it -- it can only be resolved by an upstream fix to the problematic implementation.)

You likely have a diff which isn't JSON-encodable (for example, it affects non-utf8 files). T5955 is probably the pathway forward here.

@joncalhoun: That's not related to this ticket, and also not supported. You can add projects to Revisions, but not Diffs. There will be an API for projects on Revisions eventually, see T5873.

This is a pretty old ticket, but if possible I'd like to add a use case: