Thank you for your contribution and feedback! Help us review faster by providing the following information:
This issue is a: (mark with an x)
[ ] bug report
[ ] request for new sample
[x] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)
Steps to reproduce:
n/a
Errors and log messages:
n/a
Expected behavior:
The cognitive services taxonomy has been evolved over time. Nowadays we have top-level grouping (Vision/Speech/Knowledge/Search/Language), and under these, you have various services. Since the current set of golang sources are all about search, they should be moved one level deeper. This would make the namespace align better with other language SDKs (e.g. com.microsoft.azure.cognitiveservices.search.websearch.)
Thank you for your contribution and feedback! Help us review faster by providing the following information:
This issue is a: (mark with an
x)Steps to reproduce:
n/a
Errors and log messages:
n/a
Expected behavior:
The cognitive services taxonomy has been evolved over time. Nowadays we have top-level grouping (Vision/Speech/Knowledge/Search/Language), and under these, you have various services. Since the current set of golang sources are all about search, they should be moved one level deeper. This would make the namespace align better with other language SDKs (e.g. com.microsoft.azure.cognitiveservices.search.websearch.)
OS and Go versions:
all
Further info: