Skip to content

Commit 6453e56

Browse files
authored
Mention quiet when documenting null-event SelectionEvents
I wondered where these came from, ended up searching through the code source (it was quite easy mind you, which means the code base is not too bad :p) The solution was to set `quiet` to true on my functions.
1 parent 9d902cd commit 6453e56

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/pages/api-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -371,7 +371,7 @@ interface SelectionEvent {
371371
}
372372
```
373373

374-
- `event` - The original event that triggered the selection, may be `null` if manually triggered.
374+
- `event` - The original event that triggered the selection, may be `null` if manually triggered. Set `quiet` to true in manual selection functions to prevent firing the event. (see `clearSelection`, `select` or `unselect`)
375375
- `store` - The current state of the selection store.
376376
- `selection` - The selection area instance.
377377

0 commit comments

Comments
 (0)