Repository navigation
Document that a custom Inspect implementation shows redacted fields - #4805
Merged
Merged
Conversation
Fields marked with `redact: true` are only excluded from inspect on the schema when Ecto derives Inspect for it. When the schema derives or implements Inspect itself, that implementation is used and redacted fields are shown unless it excludes them.
josevalim
approved these changes
Oct 19, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fields marked with
redact: trueare only excluded from inspect on the schema when Ecto derivesInspectfor it. When the schema derives or implementsInspectitself, that implementation is used and redacted fields are shown unless it excludes them. The docs only mentioned@derive_inspect_for_redacted_fields falseas the exception.