Show friendly name in repair issue and flow#11
Merged
Conversation
Resolve the remote's friendly name from the entity registry and use it in the repair issue title and fix flow confirm step. Falls back to the entity_id when no name is available. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The entity registry often has no name/original_name set. Fall back to state.name (the friendly_name attribute) in config flow, repair issue creation, and repair flow name resolution. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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.
Summary
nameororiginal_name), falling back toentity_iddataso the repair flow can use it without an extra lookup{name}placeholderTest plan
ruff check+ruff format)🤖 Generated with Claude Code