Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(ui): navigate up/down on the calls page from the peek drawer #2798

Merged
merged 11 commits into from
Nov 5, 2024

Conversation

gtarpenning
Copy link
Member

@gtarpenning gtarpenning commented Oct 28, 2024

Description

WB-21663

use shift + up arrow or shift + down arrow to control the selected call in the calls table.

implementation can be extended to the other main page tables, although the rowIds behave slightly differently.

Testing

How was this PR tested?

@circle-job-mirror
Copy link

@gtarpenning gtarpenning marked this pull request as ready for review October 30, 2024 00:07
@gtarpenning gtarpenning requested review from a team as code owners October 30, 2024 00:07

const getNextRowId = useCallback(
(currentId: string) => {
console.log('getNextRowId', currentId, rowIds);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dev tracks

@@ -479,6 +481,15 @@ export const CallsTable: FC<{
}
}
}, [rowIds, peekId]);
const {setRowIds} = useContext(TableRowSelectionContext);
useEffect(() => {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i would use const {isPeeking} = useContext(WeaveflowPeekContext); instead

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

which returns true if the component is inside a peek drawer

active={showTraceTree ?? false}
onClick={onToggleTraceTree}
/>
<Box
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems like these should only be present if it is peaking AND there are row ids set in the context. I think these arrows will show up on the primary call page right now

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, fixed.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screenshot 2024-11-04 at 07 58 30 This flex-box puts the tree expansion to the left when full screen (since space-between) will left justify if there is a single element.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screenshot 2024-11-04 at 10 49 54 AM Screenshot 2024-11-04 at 10 50 08 AM oops, fixed

@gtarpenning gtarpenning requested a review from tssweeney November 1, 2024 19:47
@gtarpenning gtarpenning enabled auto-merge (squash) November 5, 2024 00:44
@gtarpenning gtarpenning merged commit abe4fea into master Nov 5, 2024
112 of 115 checks passed
@gtarpenning gtarpenning deleted the griffin/hotkey-next-call branch November 5, 2024 16:52
@github-actions github-actions bot locked and limited conversation to collaborators Nov 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants