Skip to content

Commit b070abd

Browse files
authored
Update src/connections/sources/catalog/libraries/mobile/react-native/index.md
1 parent 38aff64 commit b070abd

File tree

1 file changed

+1
-1
lines changed
  • src/connections/sources/catalog/libraries/mobile/react-native

1 file changed

+1
-1
lines changed

src/connections/sources/catalog/libraries/mobile/react-native/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -390,7 +390,7 @@ const unsubscribe = NetInfo.addEventListener((state) => {
390390
You can create a custom Flush Policy special for your application needs by implementing the `FlushPolicy` interface. You can also extend the `FlushPolicyBase` class that already creates and handles the `shouldFlush` value reset.
391391
A `FlushPolicy` only needs to implement two methods:
392392
- `start()`: Executed when the flush policy is enabled and added to the client. This is a good place to start background operations, make async calls, configure things before execution
393-
- `onEvent(event: SegmentEvent)`: Gets called on every event tracked by your client
393+
- `onEvent(event: SegmentEvent)`: Called on every event tracked by your client
394394
- `reset()`: Called after a flush is triggered (either by your policy, by another policy, or manually)
395395
Your policies also have a `shouldFlush` observable boolean value. When this is set to true the client attempts to upload events. Each policy should reset this value to `false` according to its own logic, although it's common to do it inside the `reset` method.
396396
```ts

0 commit comments

Comments
 (0)