Repository navigation
Mask the panel's time zone and country code in the tree export - #237
Merged
Merged
Conversation
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
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.
The masked device-tree export (#229) kept
time-zoneandcountry-codeas published. The Home Assistant integration that forwards the export in diagnostics already redacts the time zone, and its privacy tests treat both as site values, so the export now masks them by property id on any node, asUTCandZZ(valid placeholders, so a reader such asebus-panel-simstill parses the export). Ships in the unpublished 3.8.0b2 / 1.4.0b4.Testing: full suite 2229 passed, 7 skipped, 9 xfailed; the leak test now plants distinct values for both, and the new mask assertions fail without the change.