-
Notifications
You must be signed in to change notification settings - Fork 21
Status - add export logic for two-layer aggregation #566
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…into sb-groupexport
…into sb-groupexport
…into sb-groupexport
Can we remove this? Seems like the specific JSON serialization is an implementation detail so simpler is better. Refers to: src/StatusAggregator/Export/StatusContractResolver.cs:15 in e7c586e. [](commit_id = e7c586e, deletion_comment = False) |
|
||
if (currentComponent == null) | ||
{ | ||
_logger.LogWarning("Couldn't find component corresponding to active entities."); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LogWarning [](start = 36, length = 10)
Why isn't this an exception?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my bad, will fix
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…into sb-groupexport
…into sb-groupexport
…into sb-groupexport
This PR fixes the export logic (that generates the
status.json
file) that was broken by #563.Previously, only
EventEntity
s were exported--now we need to exportIncidentGroupEntity
s as well.I would suggest starting at
StatusExporter
.