communication/azure-communication-sms - cspell found spelling errors in source code #22638
Assignees
Labels
Comments
danieljurek
added
Client
danieljurek
changed the title
|
Note: the files in the |
|
Once fixed, we should remove the package from the spellchecker whitelist - #22199 |
azure-sdk
pushed a commit
to azure-sdk/azure-sdk-for-python
that referenced
this issue
Mar 7, 2023
Adding version 2023-01-01-preview with User API Key changes for Elastic (Azure#22638) * Base API Commit * Changing API version to 2023-02-01-preview * Adding new getOrganizationApiKey post API * Adding returnApiKey property in ElasticMonitorResource * Updating getOrganizationApiKey URI * Adding SubscriptionIdParameter in getOrganizationApiKey * Renaming ex to Organizations_GetApiKey * Updating description for UserApiKeyResponse * Updating examples * Updating readme.md * Updated Depolyment Info, added marketplace info * prettier check fixed * model validation fixed * validation fix * prettier fix * Increasing max length limit of companyName and business from 50 to 100 * Increasing companyName and business max length limits to 100 in all versions * Revert "Increasing companyName and business max length limits to 100 in all versions" This reverts commit c8977b64daa962bce70d33a325053294a4875610. * Revert "Increasing max length limit of companyName and business from 50 to 100" This reverts commit 7bd354775b3a57abf310a351c75763bc1aa121f3. * Updating summary for getOrganizationApiKey * Renaming "returnApiKey" to "generateApiKey" * Adding "x-ms-secret": true for apiKey * Updating getOrganizationApiKey API to /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Elastic/monitors/{monitorName}/getOrganizationApiKey * Rearranging APIs * Adding "consumes" to getOrganizationApiKey * Changing case of emailId * Moving the API under paths * Updating User and Company related properties' max length limit to 64 * Adding Location in response header of LROs * Updating getOrganizationApiKey path * Updating getOrganizationApiKey Summary --------- Co-authored-by: Rhea Hooda <rheahooda@microsoft.com>
|
Hi @danieljurek, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Spell check scanning of package at
sdk/communication/azure-communication-smsdetected spelling errors in the source code and related files. This directory is opted out of PR spell checking in PR #22199 to keep PRs unblocked.What to do
.vscode/cspell.json'signorePathsfield. It will look like:sdk/communication/azure-communication-sms/**. You need to do this to enable checking the files../eng/common/spelling/Invoke-Cspell.ps1 -ScanGlobs "sdk/communication/azure-communication-sms/**".vscode/cspell.jsonwhere theignorePathsis updated to remove the entry for this service.). You may need to rungit add -f .vscode/cspell.jsonto force adding the changes to the file in git.Spell checking output
The text was updated successfully, but these errors were encountered: