Best way to report an implementation error in the Content Server REST API?

I've encountered two small but potentially breaking issues when working with Categories via REST.

Attempting to add a category by POSTing /api/v2/nodes/{id}/categories/ to a node that already has the specified category applied returns a 500. The posted documentation for all versions of the API state that it should be returned as a 400.

Also, there is a small typo between the documented reason text and the error value that is actually being returned - insignificant yes, but enough to break an .endsWith() string evaluation. This is also present the API documentation for all versions.

I haven't had the best success in the past working with the customer support team to report this type of issue. Is there a better venue since the latest overhaul of the Developer ecosystem, or do I need to go irritate those poor people again?

Find more posts tagged with

Comments

Pramod Mohandas

From my past experience, the best way to report such issues is still going via the Support channel route so that all reported issues can be centralized and redirected to the right team for further investigation and updates.

Kris Boutilier

Makes sense. I'll put on a smile and send them yet another ticket...

It's a shame there's no way to easily see what has already been reported/acknowledged and/or fixed so I can prevent wasted effort on everyone's part if I'm facing something that is already known about. I've also encountered a nasty little concurrency issue with Connected Workspace REST calls in 16.2.11 that only appears at scale, and I'm certain someone else must have already reported it by now - but I can't see a patch for it anywhere either.