This repository was archived by the owner on Sep 3, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 642
(feat) add entity and trigger views to signal instance page #6105
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
whitdog47
approved these changes
Jul 2, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Adds views to the signal instance table to provide basic summary statistics per entity and per snooze filter.
Backend changes
SignalFilterReadPydantic model to include the backreference to the associated signal. UsesSignalBaseto avoid recursive dependency.Frontend changes
TableInstance.vueinto four files: a parent file of the same name that sets the active table view, and three dedicated table files for each respective grouping.instance/directory alongside the now three signal views.MultiSignalPopovercomponent to display the (potentially multiple) signals that may be associated with a given signal filter.store.jsin theinstance/directory to handle API calls dedicated to the different views.