sdk/purview/azure-analytics-purview-administration - cspell found spelling errors in package

[jairmyree]

Spell check scanning of package at sdk/purview/azure-analytics-purview-administration detected spelling errors in the public API surface. This directory is opted out of PR spell checking in PR #31526 to keep PRs unblocked.

What to do

1. Ensure Node.js is installed (https://nodejs.org/en/download/).
2. Delete the entry in .vscode/cspell.json's ignorePaths field. It will look like: sdk/purview/azure-analytics-purview-administration/**. You need to do this to enable checking the files.
3. From the root of the repo run spell check using ./eng/common/spelling/Invoke-Cspell.ps1 -ScanGlobs "sdk/purview/azure-analytics-purview-administration/**"
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

./sdk/purview/azure-analytics-purview-administration/src/samples/java/com/azure/analytics/purview/administration/generated/MetadataPolicyUpdate.java:26:703 - Unknown word (myparentcollection)
./sdk/purview/azure-analytics-purview-administration/src/samples/java/com/azure/analytics/purview/administration/generated/MetadataPolicyUpdate.java:26:1102 - Unknown word (myparentcollection)
./sdk/purview/azure-analytics-purview-administration/src/samples/java/com/azure/analytics/purview/administration/generated/MetadataPolicyUpdate.java:26:1509 - Unknown word (myparentcollection)
./sdk/purview/azure-analytics-purview-administration/src/samples/java/com/azure/analytics/purview/administration/generated/ResourceSetRulesCreateOrUpdateResourceSetRule.java:24:5588 - Unknown word (XLSB)

[github-actions]

Hi @jairmyree, we deeply appreciate your input into this project. Regrettably, this issue has remained unresolved for over 2 years and inactive for 30 days, 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.