You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we have an Action subscribing to an ESE but which only handles 1 event and ignores the rest. The generated trace for an event that is ignored still includes a span for the Action. Additionally, the span is wrongly marked as belonging to the existing handler.
Example:
GetRandomPhotoActionAsync handles only UserAdded events so HandleAdd is the only declared handler there
however, when a UserNameChanged is produced, we get a span Action : GetRandomPhotoActionAsync HandleAddas shown below.
Ideally, I think we should not produce a span for ignored events. But if we must, then would be better to have it named correctly.
The text was updated successfully, but these errors were encountered:
When we have an Action subscribing to an ESE but which only handles 1 event and ignores the rest. The generated trace for an event that is ignored still includes a span for the Action. Additionally, the span is wrongly marked as belonging to the existing handler.
Example:
GetRandomPhotoActionAsync
handles onlyUserAdded
events soHandleAdd
is the only declared handler thereUserNameChanged
is produced, we get a spanAction : GetRandomPhotoActionAsync HandleAdd
as shown below.Ideally, I think we should not produce a span for ignored events. But if we must, then would be better to have it named correctly.
The text was updated successfully, but these errors were encountered: