bQUARKz
6e594c15d7
All checks were successful
JaCoCo Coverage #### Project Overview
No changes detected, that affect the code coverage.
* Line Coverage: 61.37% (17351/28272)
* Branch Coverage: 52.31% (6722/12850)
* Lines of Code: 28272
* Cyclomatic Complexity: 11325
#### Quality Gates Summary
Output truncated.
Test / Build skipped: 15, passed: 601
Intrepid/Prometeu/Studio/pipeline/head This commit looks good
63 lines
2.1 KiB
Markdown
63 lines
2.1 KiB
Markdown
---
|
|
id: AGD-0045
|
|
ticket: pbs-lsp-workspace-symbols
|
|
title: PBS LSP Workspace Symbols
|
|
status: open
|
|
created: 2026-07-15
|
|
resolved:
|
|
decision:
|
|
tags: [studio, lsp, vscode, compiler-pbs, editor, workspace-symbols]
|
|
---
|
|
|
|
## Pain
|
|
|
|
Domain owner: `studio/lsp`
|
|
|
|
VS Code cannot search PBS symbols across the workspace, so users cannot quickly jump to functions, services, structs, constants, or stdlib-exposed APIs by name.
|
|
|
|
## Context
|
|
|
|
Document-level editorial features exist, but the LSP does not announce workspaceSymbolProvider and the compiler pipeline does not expose a project-wide symbol index designed for editor queries.
|
|
|
|
## Open Questions
|
|
|
|
- [ ] Should workspace symbols include only project files or also imported stdlib and SDK surfaces?
|
|
- [ ] What symbol kinds and ranking should be returned for duplicate names or overloads?
|
|
- [ ] Should the symbol index be cached from analysis snapshots or rebuilt per request in the first implementation?
|
|
|
|
## Options
|
|
|
|
### Option A - Project source index only
|
|
|
|
- **Approach:** Index project-owned declarations from analysis snapshots and expose `workspace/symbol`.
|
|
- **Pro:** Clear ownership and physical locations.
|
|
- **Con:** Does not help users discover stdlib/SDK symbols.
|
|
- **Maintainability:** Strong as a first wave.
|
|
|
|
### Option B - Project plus stdlib index
|
|
|
|
- **Approach:** Include project declarations and imported stdlib/SDK surfaces in the workspace symbol result set.
|
|
- **Pro:** Better discovery, especially for new users.
|
|
- **Con:** Requires a navigation policy for stdlib source or virtual targets.
|
|
- **Maintainability:** Good if stdlib target handling is solved; awkward otherwise.
|
|
|
|
## Tradeoffs
|
|
|
|
Workspace symbols are partly navigation and partly discovery. Including stdlib too early can create broken jumps if target locations are not defined.
|
|
|
|
## Recommendation
|
|
|
|
Prefer Option A first, then add stdlib once definition has a target policy.
|
|
|
|
## Discussion
|
|
|
|
This should follow document symbols and the semantic location/index work.
|
|
|
|
## Resolution
|
|
|
|
Ainda em aberto.
|
|
|
|
## Next Step
|
|
|
|
Decide whether first-wave workspace search includes stdlib or project-only symbols.
|