This repository was archived by the owner on Sep 3, 2025. It is now read-only.
feat(signal): adding historical events to signal definitions #5759
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.
This pull request introduces the capability to log and view create and update events associated with signal definitions. This enhancement allows users to track changes and updates to signals over time, providing greater transparency and traceability.
Key Changes
Database Schema Update:
signal_idto theeventtable to establish a relationship between events and signals.Model Updates:
EventandSignalmodels to include relationships for tracking events.Service Enhancements:
log_signal_eventfunction to log events related to signal creation and updates.createandupdatefunctions in the signal service to log events whenever a signal is created or updated.API Changes:
create_signalandupdate_signalendpoints to include the current user, enabling event logging with user context.Frontend Additions:
HistoryViewer.vuecomponent to display the timeline of events for a signal.Sample screenshot