[front] - fix: manage assistant tabs #8352
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
October 30, 2024 18:28
…ants - Replace direct href manipulation with scope state management for tab selection - Ensure tab scope uses appropriate `AgentsGetViewType` type during API calls - Simplify activeTab computation by using scope value directly instead of label - Adjust assistant filtering logic to use the updated selectedTab state
- Use object property shorthand for the scope assignment in assistant mapping
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR aims at fixing the tab switch in the manage assistant view, which was caused by wrong attributes being accessed
Risk
Low
Deploy Plan
Deploy
front