Given implementation experience, was choosing the "controller style endpoint" pattern the right decision?

[msporny]

@mprorock wrote:

Note in section 2.1.4 of the REST guide the examples - there are good reasons in REST to utilize an ID or name in the path. Prior iterations of that guide were less clear which caused confusion and folks removing those items to just the request body which then breaks the notion of ensuring that when a resource is identified, that that resource identification occurs in the URI. -- via comment on PR #255

It sounds like @mprorock is challenging the "controller style endpoint" pattern that the group provisionally agreed to. If that is the case, I agree with @mprorock -- I've never liked the "controller style endpoint" pattern and we should see if the group has new opinions on this now that we have some implementation experience under our belt.

[msporny]

The group discussed this on the 2022-02-08 telecon and agreed that they are open to proposals to modify existing or add new API endpoints that follow collection-style naming conventions.

PRs welcome.