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
fix(event processor): If batchSize = 0 or flushInterval = 0, log that values are invalid and use default values instead (#342)
Summary;
Add/change validation for maxQueueSize and flushInterval inputs to AbstractEventProcessor. When invalid, ignore and use default values.
Test plan:
New unit tests
Issues:
https://optimizely.atlassian.net/browse/OASIS-5167
Copy file name to clipboardExpand all lines: packages/event-processor/CHANGELOG.MD
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
7
7
## [Unreleased]
8
8
Changes that have landed but are not yet released.
9
9
10
+
### New Features
11
+
- In `AbstractEventProcessor`, validate maxQueueSize and flushInterval; ignore & use default values when invalid
12
+
-`AbstractEventProcessor` can be constructed with a `notificationCenter`. When `notificationCenter` is provided, it triggers a log event notification after the event is sent to the event dispatcher
13
+
14
+
### Changed
15
+
- Removed transformers, interceptors, and callbacks from `AbstractEventProcessor`
16
+
10
17
## [0.2.1] - June 6, 2019
11
18
12
19
- Wrap the `callback` in `try/catch` when implementing a custom `eventDispatcher`. This ensures invoking the `callback` will always cleanup any pending retry tasks.
@@ -18,4 +25,4 @@ events that did not send successfully due to page navigation
0 commit comments