Advanced search OR/parentheses in section filters returns no results (works fine via `gh pr list --search`)
Describe the bug
Using GitHub's advanced search boolean syntax (AND/OR with parentheses) in a section's filters config returns no/incorrect results in gh-dash, even though the identical query string works correctly when run directly via gh pr list --search or gh search prs.
Steps to reproduce
Confirm the query works via plain gh CLI:
gh pr list --search 'org:myorg (assignee:@me OR author:@me)'→ returns expected PRsAdd the same string as a gh-dash section filter:
prSections:
- title: "Mine"
filters: `org:myorg (assignee:@me OR author:@me)`- Launch gh-dash → section returns no results / incorrect results.
Or using
/search and pasting -> same empty result
Expected behavior
Since gh CLI (v2.79.0+) supports advanced issue/PR search (AND/OR, nested parentheses) via the advanced_search GraphQL/REST parameter, gh-dash's section filters should support the same syntax, since it's documented as passing arbitrary GitHub search qualifiers.
Suspected cause
gh-dash appears to build its own GraphQL search queries via go-gh rather than shelling out to gh <cmd> --search, and may not be requesting the ISSUE_ADVANCED search type/advanced_search=true parameter that GitHub's API needs to parse boolean logic. Without it, the query silently falls back to the classic search engine where OR is treated as a literal token.
Environment
- gh-dash version:
gh-dash version dev
goos: darwin
goarch: arm64
module version: v4.25.2, checksum: h1:i24BUObEJkr0/i1Dt0wEWOBecKMYFqC6J0uQhXTt8NI=- gh version:
gh version 2.97.0 (2026-07-31)
https://github.com/cli/cli/releases/tag/v2.97.0Source: dlvhdr/gh-dash