A language for describing resource-oriented APIs & turning them into Swagger or resource diagrams. Oriented around the concepts we want to expose in the APIs.
Would it be possible to remove the id parameter from MULTIGET endpoints? The id parameter is redundant as the use cases it supports could be covered by defining a GET endpoint instead. Leaving it in makes the intended use of the MULTIGET confusing as a user could provide a single Resource id and expect to get multiple Resources back.
Then again, I could just be missing the point entirely and there might be a perfectly valid use case for this feature. DM is making extensive use of the MULTIGET in the Field API and it would clean up our interface if it was removed.
Would it be possible to remove the
idparameter from MULTIGET endpoints? Theidparameter is redundant as the use cases it supports could be covered by defining aGETendpoint instead. Leaving it in makes the intended use of theMULTIGETconfusing as a user could provide a single Resource id and expect to get multiple Resources back.Then again, I could just be missing the point entirely and there might be a perfectly valid use case for this feature. DM is making extensive use of the MULTIGET in the Field API and it would clean up our interface if it was removed.