Skip to content

🐛 fix: ensure events only fire when public methods return valid data#215

Open
DerAndereAndi wants to merge 1 commit intodevfrom
fix/event-firing-consistency
Open

🐛 fix: ensure events only fire when public methods return valid data#215
DerAndereAndi wants to merge 1 commit intodevfrom
fix/event-firing-consistency

Conversation

@DerAndereAndi
Copy link
Copy Markdown
Member

  • Fix DeviceConfiguration OR/AND precedence bug in CheckEventPayloadDataForFilter (item.KeyId match was OR'd with item.Value != nil instead of AND'd, causing the filter to accept any keyvalue item with a value regardless of KeyId)
  • Gate 11 event handlers across EG LPC, MA MGCP, and MA MPC on a successful public-method call so event notifications stay consistent with the data consumers can actually retrieve via the public API
  • Update event tests accordingly

- Fix DeviceConfiguration OR/AND precedence bug in CheckEventPayloadDataForFilter
  (item.KeyId match was OR'd with item.Value != nil instead of AND'd, causing
  the filter to accept any keyvalue item with a value regardless of KeyId)
- Gate 11 event handlers across EG LPC, MA MGCP, and MA MPC on a successful
  public-method call so event notifications stay consistent with the data
  consumers can actually retrieve via the public API
- Update event tests accordingly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant