[COMPASS-6691] Stores in query-history emit actions twice Created: 01/Apr/23 Updated: 27/Oct/23 Resolved: 13/Jul/23 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Query History |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sergey Petushkov | Assignee: | Unassigned |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OS: |
||
| Epic Link: | COMPASS-5490 |
| Documentation Changes: | Not Needed |
| Description |
|
Query history fires runQuery when clicking on a single item in the list twice, it doesn't matter if you clicked in the recents or favorites list, runQuery action will be executed in both stores. This doesn't have any noticeable effect on the app, but this means that we are reporting wrong telemetry for these events as any query selection results in two telemetry function calls |