Assigned
Status Update
Comments
pu...@google.com <pu...@google.com>
pu...@google.com <pu...@google.com>
ni...@carsync.io <ni...@carsync.io> #2
Hello,
To assist us in conducting thorough investigation, we kindly request your cooperation in providing the following information regarding the reported issue:
- Has this scenario ever worked as expected in the past?
- Do you see this issue constantly or intermittently ?
- If this issue is seen intermittently, then how often do you observe this issue ? Is there any specific scenario or time at which this issue is observed ?
- To help us understand the issue better, please provide detailed steps to reliably reproduce the problem.
- It would be greatly helpful if you could attach screenshots of the output related to this issue.
Your cooperation in providing these details will enable us to dive deeper into the matter and work towards a prompt resolution. We appreciate your assistance and look forward to resolving this issue for you.
Thank you for your understanding and cooperation.
Description
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish: It seems labeling documents is not supported at the moment through API (rest/rpc/client lib/http) request at the moment (Looked through our documented reference here:
How this might work:
If applicable, reasons why alternative solutions are not sufficient: It is available through UI but missing in rest/rpc/client library which may more efficient from the community poster use case:
Other information (workarounds you have tried, documentation consulted, etc):