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

Spelling #4119

Merged
merged 145 commits into from
Mar 20, 2018
Merged

Spelling #4119

merged 145 commits into from
Mar 20, 2018

Conversation

jsoref
Copy link
Contributor

@jsoref jsoref commented Mar 11, 2018

Generated by https://github.com/jsoref/spelling f; to maintain your repo, please consider fchurn

Copy link
Contributor

@vishalnayak vishalnayak left a comment

Choose a reason for hiding this comment

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

Other than the commented items, this looks good.

@@ -135,7 +135,7 @@ func (b *databaseBackend) DatabaseConfig(ctx context.Context, s logical.Storage,
type upgradeStatements struct {
// This json tag has a typo in it, the new version does not. This
// necessitates this upgrade logic.
CreationStatements string `json:"creation_statments"`
CreationStatements string `json:"creation_statements"`
Copy link
Contributor

Choose a reason for hiding this comment

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

[For others in the Vault team] This may not be required.

Copy link
Member

Choose a reason for hiding this comment

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

In fact, this would break things because this is on purpose. The real question is, since this commit is automated, will the author respond to comments.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There's a sleepy human behind this. I'll drop this

@@ -144,7 +144,7 @@ type upgradeStatements struct {
type upgradeCheck struct {
// This json tag has a typo in it, the new version does not. This
// necessitates this upgrade logic.
Statements upgradeStatements `json:"statments"`
Statements upgradeStatements `json:"statements"`
Copy link
Contributor

Choose a reason for hiding this comment

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

[For others in the Vault team] This may not be required.

Copy link
Member

Choose a reason for hiding this comment

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

Will also break things.

@@ -147,7 +147,7 @@ func TestBackend_RoleUpgrade(t *testing.T) {
}

// Upgrade case
badJSON := `{"statments":{"creation_statments":"test","revocation_statements":"","rollback_statements":"","renew_statements":""}}`
badJSON := `{"statements":{"creation_statements":"test","revocation_statements":"","rollback_statements":"","renew_statements":""}}`
Copy link
Contributor

Choose a reason for hiding this comment

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

[For others in the Vault team] This may not be required.

Copy link
Member

Choose a reason for hiding this comment

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

Will break things.

@jsoref
Copy link
Contributor Author

jsoref commented Mar 14, 2018

@jefferai: dropped. fwiw, my general advice is to use things like:
creation_statements_ instead of creation_statments assuming that you're just trying to show "X" isn't a thing, there's no particular reason to actually use a misspelling per se.

@jefferai
Copy link
Member

@jsoref that particular misspelling is in an upgrade path that's there specifically to migrate people from an original mistaken spelling to a fixed version :-)

@jefferai
Copy link
Member

Looks good, thanks!

@jefferai jefferai merged commit e43b76e into hashicorp:master Mar 20, 2018
@jefferai jefferai added this to the 0.9.6 milestone Mar 20, 2018
@jsoref jsoref deleted the spelling branch March 20, 2018 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants