Feat: SK-Zones-definition-integration #388
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
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.
Major refactoring. Retires local KIP zones in favor of SK defined Zones. Using Zones now requires using the Edit zones SK plugin for zones definition (for the time being - until we can delete SK meta keys).
New Notification service and Menu now supports silencing and clearing SK server notifications for improved integration.
Simplified Zones Settings panel (for the time being).
Gauges now support 4 zone colors.
Path value subjects now emits path: value, timestamp and data state for simpler Gauge integration.
Many delta and data service processing improvements and general performance optimyzations.