feat(docs): tag filter in search and tag display on request pages (BRU-4028) - #60
Open
sundram-bruno wants to merge 3 commits into
Open
feat(docs): tag filter in search and tag display on request pages (BRU-4028)#60sundram-bruno wants to merge 3 commits into
sundram-bruno wants to merge 3 commits into
Conversation
…U-4028) Replaces the search palette's folder dropdown with a multi-select tag filter (a record must carry every selected tag) and shows an item's tags on the request, folder and overview pages. Tags are read from both the info block and legacy root-level fields, and requests inherit their ancestor folders' tags for filtering. Also fixes descender clipping in shared dropdown options and adds the missing vertical gap between stacked right-column sections.
Trim and dedupe tags at the source so hand-edited files cannot produce duplicate chips or whitespace-distinct filter entries. Mark the tag filter listbox as multi-select for assistive technology, style the overview tag row, and replace the order-dependent tag trigger locator with a derived test id. Tag page tests get their own describe and POM locator, and the search suite now covers tag-filtered typed queries and the Clear all reset.
sundram-bruno
force-pushed
the
feat/bru-4028-docs-tag-filter
branch
from
August 25, 2026 20:46
25d2930 to
5903a09
Compare
Request pages now display tags inherited from ancestor folders as muted chips with an inherited-count badge, matching how inherited auth and headers are presented. Tag casts follow the string[] contract the Bruno app saves, the tag menu and trigger expose derived test ids, the tag filter listbox is announced as multi-select, and the new specs render through useRenderToDom. Also fixes two surfaced bugs: graphql requests were absent from search records entirely (own nav page type was never indexed), and the gRPC page swallowed tags when the request had no other configuration. The testbench now covers chained inheritance, mixed own/inherited chips, own-over-inherited dedupe, tagged websockets and collection-level tags.
sachin-bruno
approved these changes
Aug 26, 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
2 participants
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.
JIRA: BRU-4028
Readers can now filter the search palette by tags: the folder dropdown is replaced with a multi-select Tags filter that narrows results to items carrying every selected tag, working alongside the text query and method chips. Tags inherited from ancestor folders count for filtering, and collections without tags show no filter at all.
Request pages (HTTP, GraphQL and gRPC) now display the request's tags in a Tags section below the code snippet; folder and overview pages show their tags too once the data carries them. Tags are read from both the info block and legacy root-level fields, so hand-edited collections work.
Screen.Recording.2026-08-26.at.6.43.22.PM.mov