feat(designer-v2): Add hiddenBrowseCategories configuration option#9072
Open
SakoPak wants to merge 2 commits intoAzure:mainfrom
Open
feat(designer-v2): Add hiddenBrowseCategories configuration option#9072SakoPak wants to merge 2 commits intoAzure:mainfrom
SakoPak wants to merge 2 commits intoAzure:mainfrom
Conversation
🔒 AI Validation PendingThis PR is from an external contributor. AI validation will be performed after manual review by a maintainer. Maintainers: Add the |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a host-configurable hiddenBrowseCategories option to Designer V2 so different host environments can hide specific browse panel categories without introducing new one-off feature flags.
Changes:
- Extend browse category helpers to accept a
hiddenCategorieslist and mark matching categories asvisible: false. - Wire the new
hiddenBrowseCategorieshost option into the browse panel via a Redux selector. - Add unit tests covering hidden category behavior for both trigger and action categories.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| libs/designer-v2/src/lib/ui/panel/recommendation/browse/helper.ts | Adds optional hiddenCategories param to category builders and applies filtering via visible: false. |
| libs/designer-v2/src/lib/ui/panel/recommendation/browse/browseView.tsx | Reads hiddenBrowseCategories from state and passes it into category builders. |
| libs/designer-v2/src/lib/ui/panel/recommendation/browse/test/helper.spec.ts | Adds tests validating hidden category behavior (but currently duplicated). |
| libs/designer-v2/src/lib/core/state/designerOptions/designerOptionsSelectors.ts | Adds useHiddenBrowseCategories selector for host-provided hidden keys. |
| libs/designer-v2/src/lib/core/state/designerOptions/designerOptionsInterfaces.ts | Adds hiddenBrowseCategories?: string[] to hostOptions typing. |
- Use EMPTY_ARRAY constant to prevent unnecessary re-renders - Remove duplicate test block in helper.spec.ts - Update browseView.spec.tsx assertions for 4th parameter
This was referenced Apr 18, 2026
This file contains hidden or 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
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.
Commit Type
Risk Level
What & Why
Problem: Different host environments (Azure Portal, VS Code, Power Automate, ACR Workflow Factory) need to customize which browse panel categories are visible to users. The current approach uses one-off boolean flags (e.g.,
disableMcpClientTools) which requires code changes for each new category to hide.Solution: Adds a generic
hiddenBrowseCategoriesconfiguration option that accepts an array of category keys. This allows any host to hide any combination of the 15 available categories (8 triggers + 7 actions) without library modifications.Benefits:
['aiAgent', 'humanInTheLoop']or['favorites', 'simpleOperations']Example Use Case: ACR Workflow Factory can hide AI Agent and Human in the Loop categories to streamline their workflow authoring experience, while Power Automate could hide different categories based on their specific needs.
Impact of Change
hiddenBrowseCategories: string[]property inhostOptions. Follows existing pattern used bydisableMcpClientTools. No breaking changes - defaults to empty array (all categories visible)..includes()check on category keys.Test Plan
15 unit tests added in helper.spec.ts
Contributors
Screenshots/Videos
manual testing - hiding the 'AI Agent' and 'Human in the loop' category
Before: Browse panel showing all categories including "AI Agent" and "Human in the Loop"
After: Browse panel with those categories hidden