-
Notifications
You must be signed in to change notification settings - Fork 189
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 @sensitive handling in Display implementations on error shapes #1802
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A new generated diff is ready to view.
A new doc preview is ready to view. |
A new generated diff is ready to view.
A new doc preview is ready to view. |
A new generated diff is ready to view.
A new doc preview is ready to view. |
A new generated diff is ready to view.
A new doc preview is ready to view. |
jjant
added
the
needs-review
A tag for PRs waiting on a review from one of the repo admins
label
Oct 4, 2022
jjant
changed the title
Fix @sensitive handling in Display implementations on structures
Fix @sensitive handling in Display implementations on error shapes
Oct 5, 2022
hlbarber
approved these changes
Oct 7, 2022
A new generated diff is ready to view.
A new doc preview is ready to view. |
hlbarber
pushed a commit
that referenced
this pull request
Oct 7, 2022
…1802) * Use `Sensitive` wrapper in Debug impl for structures * Fix using the wrong import path for `Sensitive` * Use redactMemberIfNecessary * Fix display implementation on errors to respect @sensitive trait * Don't use Sensitive type just yet * Add entry in changelog * Improve redaction of sensitive error message * Use correct flags in changelog * Run ktlint
Velfi
removed
the
needs-review
A tag for PRs waiting on a review from one of the repo admins
label
Dec 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
Addresses #1743.
This doesn't yet use the
Sensitive
type to handle redaction of@sensitive
fields (as suggested by @hlbarber) because that type currently lives in theaws-smithy-http-server
crate, but the type is also needed by the client (see: #1804).Description
This smithy model:
Now generates:
Testing
I've manually checked the generated output compiling via
./gradlew codegen-server-test:build
.Checklist
CHANGELOG.next.toml
if I made changes to the smithy-rs codegen or runtime cratesBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.