What would you like to be added:
Currently, when sending a request to /yorkie.v1.AdminService/GetDocument, even if the project key is included in the header, the project's name still needs to be included in the request body. This inconsistency makes it challenging for users to interact with the API. To address this issue, it is necessary to define a clear REST API specification that ensures consistent usage of the project key in requests.
Why is this needed:
Having a defined REST API spec will make it easier for users to interact with the API and ensure a more intuitive usage of the project key in requests.
What would you like to be added: Currently, when sending a request to
/yorkie.v1.AdminService/GetDocument
, even if the project key is included in the header, the project's name still needs to be included in the request body. This inconsistency makes it challenging for users to interact with the API. To address this issue, it is necessary to define a clear REST API specification that ensures consistent usage of the project key in requests.Why is this needed: Having a defined REST API spec will make it easier for users to interact with the API and ensure a more intuitive usage of the project key in requests.