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.

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

Fix spelling in TF docs and related protos #46878

Closed
wants to merge 1 commit into from

Conversation

ptgott
Copy link
Contributor

@ptgott ptgott commented Sep 23, 2024

Related to #46191

Help us move to a new, more scalable spell checker based on vale by fixing spelling errors in the Terraform provider resource reference docs. This change fixes the spelling in the protobuf messages that these docs are based on.

Since the vale checker ignores words in backticks, this change wraps field/value names that would otherwise fail the spell checker in backticks.

Related to #46191

Help us move to a new, more scalable spell checker based on vale by
fixing spelling errors in the Terraform provider resource reference
docs. This change fixes the spelling in the protobuf messages that these
docs are based on.

Since the vale checker ignores words in backticks, this change wraps
field/value names that would otherwise fail the spell checker in
backticks.
Copy link

🤖 Vercel preview here: https://docs-g0el1xshu-goteleport.vercel.app/docs/ver/preview

@@ -27,7 +27,7 @@ message AuthorizedKey {
teleport.header.v1.Metadata metadata = 1;
// kind is a resource kind.
string kind = 2;
// sub_kind is an optional resource sub kind, used in some resources.
// an optional resource sub kind, used in some resources.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The generated go code was not strictly following the go guidelines, but removing the symbnol name from the description will make things worse. According to the go guidelines:

As with packages (above) and funcs (below), doc comments for types start with complete sentences naming the declared symbol. An explicit subject often makes the wording clearer, and it makes the text easier to search, whether on a web page or a command line.

I'm not sure how much we care about following go guidelines on generated go comments, but it feels wrong to have to break our style guidelines here. Maybe ask for a 3rd engineer pov before merging this.

@ptgott
Copy link
Contributor Author

ptgott commented Oct 25, 2024

This PR has been sitting around for a while, so I am going to close it in favor of ignoring the Vale spellchecker in our auto-generated references to avoid making the first iteration of this project too large.

@ptgott ptgott closed this Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/branch/v16 documentation no-changelog Indicates that a PR does not require a changelog entry size/sm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants