Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

avs - cspell found spelling errors #17150

Closed
danieljurek opened this issue Aug 26, 2021 · 1 comment
Closed

avs - cspell found spelling errors #17150

danieljurek opened this issue Aug 26, 2021 · 1 comment
Labels
Client This issue points to a problem in the data-plane of the library. EngSys This issue is impacting the engineering system.

Comments

@danieljurek
Copy link
Member

danieljurek commented Aug 26, 2021 •
edited
Loading

Spell check scanning of avs detected spelling errors. This service directory is opted out of PR spell checking in PR #17142 to keep merges unblocked.

What to do

  1. Ensure Node.js is installed (https://nodejs.org/en/download/). This will include npx
  2. Delete the service's entry in .vscode/cspell.json's ignorePaths field. It will look like: sdk/avs/**/*. You need to do this to enable checking the files.
  3. From the root of the repo run spell check using npx cspell lint --config '.vscode/cspell.json' --no-must-find-files "sdk/avs/**"
  4. Fix detections according to http://aka.ms/azsdk/engsys/spellcheck use the "False positives" section to fix false positives
  5. Check in changes (including the change to .vscode/cspell.json where the ignorePaths is updated to remove the entry for this service.). You may need to run git add -f .vscode/cspell.json to force adding the changes to the file in git.

Spell checking output

/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/index.ts:226:12 - Unknown word (nsxt)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/index.ts:231:12 - Unknown word (vcsa)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/index.ts:272:56 - Unknown word (LDAPS)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/index.ts:354:12 - Unknown word (vmotion)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/index.ts:358:3 - Unknown word (vcenter)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/index.ts:362:3 - Unknown word (nsxt)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/index.ts:367:12 - Unknown word (vcenter)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/index.ts:372:12 - Unknown word (nsxt)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/index.ts:472:12 - Unknown word (nsxt)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/index.ts:482:12 - Unknown word (vcenter)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/index.ts:487:12 - Unknown word (vcenter)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/mappers.ts:347:7 - Unknown word (nsxt)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/mappers.ts:349:26 - Unknown word (nsxt)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/mappers.ts:354:7 - Unknown word (vcsa)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/mappers.ts:356:26 - Unknown word (vcsa)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/mappers.ts:542:7 - Unknown word (vmotion)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/mappers.ts:544:37 - Unknown word (vmotion)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/mappers.ts:549:7 - Unknown word (vcenter)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/mappers.ts:550:37 - Unknown word (vcenter)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/mappers.ts:555:7 - Unknown word (nsxt)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/mappers.ts:556:37 - Unknown word (nsxt)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/mappers.ts:561:7 - Unknown word (vcenter)
/home/djurek/azure-sdk-for-js/sdk/avs/arm-avs/src/models/mappers.ts:563:37 - Unknown word (vcenter)
@danieljurek danieljurek added the Client This issue points to a problem in the data-plane of the library. label Aug 26, 2021
@ramya-rao-a ramya-rao-a added the EngSys This issue is impacting the engineering system. label Aug 27, 2021
@ramya-rao-a
Copy link
Contributor

All spell check errors are for an auto generated package and we don't intend to make any fixes for such packages

openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-js that referenced this issue Apr 8, 2022
@KacieKK @azaslonov
@ygrik @msyyc
CodeGen from PR 18478 in Azure/azure-rest-api-specs
ca8562e 
New Api-Version onboarding 2021-12-01-preview (Azure#18478)

* Adding 2021-12-01-preview as a copy of 2021-08-01

* Readme update

* Updating version in the 2021-12-01-preview folder

* update description for keyvault contract (Azure#17150)

Co-authored-by: Kacie Kang <jikang@microsoft.com>

* fix for the last cherry pick (06d2de8)

* fixing readme again

* APIM Policy fragments (Azure#16403)

* Adding the policy fragments spec

* Formatting

* Updating descriptions

* PolicyFragmentIdParameter as a string

* ID validation

* Adding fragment description

* Adding policy fragment format

* Adding raw xml format

* Addinga 202 response for creating/updating

* Generalising the resource collection

* formatting

* Moving everything to 2021-12-01

* version fix

* Adding pagination params. Generalising the IdParam

* Adding missing fields, fixing id param name

* Removing link formats. Fixing format param name

* POST list references

* name filter now supports "contains"

* PUT is always async

* Fixing header location url

* PUT can now return 200 and 201

* Adding more OData query support. Fixing examples.

* Resolving the cross breaking change

Co-authored-by: Milan Zolota <mizolota@microsoft.com>

* Added CORS and CSP configuration resources (Azure#16822)

* Added CORS and CSP settings resources.

* Added missing definitions.

* Added suppression of R4009 for apimportalsettings.json.

* Ran Prettier.

* Renamed definitions.

* Fixed references.

* Updated examples.

* Reversed change.

* Created new resource for portal settings.

* Added list example.

* Added missing collection contract.

* Added missing example. Cleaned up old ones.

* Fixed references.

* Fixed examples

* Fixed version.

* Added custom words. Fixed linting.

* Fixes.

* Fixes.

* Fixes.

* Fixes.

* Fixes.

* Fixes.

* Fixes.

* Fixes.

* Fixes.

* Fixes.

* Fixes

* Fixes.

* Fixes.

* Fixes

* Fixes

* Removed conflicting constraint.

* Updated readme.go.md.

* Reverted removing the restriction.

* Revert "Reverted removing the restriction."

This reverts commit 72d070f6ccc8231e4d4c9f22ac3a9c3090a545aa.

* Removed duplicate.

* Addressing PR comments.

* Adjusted reportUri property type in CSP config contract. (Azure#17947)

* Added missing body parameter description for content type resource. (Azure#18036)

* Igo/msal client version (Azure#17866)

* Added clientLibrary property to IdentityProvider

* fixed length for clientLibrary property

* Model validation fixes

* moved changes for clientLibrary property to the right spec file

* Update readme.md

Co-authored-by: Milan Zolota <mizolota@microsoft.com>
Co-authored-by: Kacie <35987382+KacieKK@users.noreply.github.com>
Co-authored-by: Kacie Kang <jikang@microsoft.com>
Co-authored-by: Alexander Zaslonov <zaslonov.alexander@gmail.com>
Co-authored-by: Igor O <ygrik@hotmail.com>
Co-authored-by: Yuchao Yan <yuchaoyan@microsoft.com>
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Client This issue points to a problem in the data-plane of the library. EngSys This issue is impacting the engineering system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@danieljurek @ramya-rao-a