Add activityId to the query results in the Data Explorer
- Dominant language
- TypeScript
- Stars
- 131
- Forks
- 67
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 10
Description
Having the activityId for a query available in the Data Explorer can reduce the amount of communication time required between our team and customers when troubleshooting query support tickets. Sometimes customers can face challenges when trying to get an activityId from the SDK, so having this available in the Data Explorer would be an easy alternative.
I think we used to have the activityId in the Data Explorer a couple of years back, but I'm not 100% sure. Creating this issue in case it's relatively easy to add back in.
Contributor guide
Research direction
No files or tests are named. Start by locating the Data Explorer query-results UI and determine where result fields are displayed; then trace how an activityId is available for each query. Done means the activityId is shown with query results and the relevant UI behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100