Repository navigation
[Feature request] Add aliases to workspace symbols #263
Description
Activity
Oh yea this is a good idea!
Would you be up for implementing this?
💎 Feel-ix-343 is offering a $5 bounty for this issue. View and reward the bounty at
algora.io/Feel-ix-343/markdown-oxide/issues/263👉 Got a pull request resolving this? Claim the bounty by commenting
/claim #263in your PR and joiningalgora.io- added a commit that references this issue
on Mar 10, 2026 🤖 Devin session started for this issue!
Hi! Checking in to see if this is still available to work on. I noticed the previous intent comment from ~3 weeks ago and the open PR #435. If the current PR is stalled or you would like a fresh pair of eyes on this implementation, I would be happy to help out.
/attempt #263
/attempt #263
Plan: add actual workspace-symbol alias entries, not only regression coverage. I will trace the existing metadata alias model and symbol provider, add focused tests showing aliases are returned alongside the canonical file symbol, and submit a narrow PR after cargo fmt/test.
/attempt #263
I am adding focused regression coverage that constructs a real vault with frontmatter aliases and verifies workspace symbols return those aliases both for empty client queries and alias searches.
/attempt #263
Pushed a formatting cleanup to the existing PR and verified the alias regression test still passes locally. The branch is back in a clean state on my side.
/attempt #263
Plan: aliases are already emitted by
Vault::to_symbol_informationson main; the missing piece is regression coverage proving they reachworkspace/symbolclients. I will add a focused test that builds a real vault with frontmatter aliases and verifies aliases are returned for both the empty-query listing path (Telescope/vim.lsp.buf.workspace_symbol()) and alias-name queries, while filename queries still resolve to the canonical symbol./attempt #263
Plan: alias emission already lives in
Vault::to_symbol_informationson main. Open PRs #435/#463/#467/#470 only assert symbol names. This attempt adds picker-facingcontainer_nameon alias symbols, skips empty/duplicate aliases, strengthens regression coverage (empty query, fuzzy alias query, URI/kind parity, no-alias files), and updates the docs so workspace symbols mention frontmatter aliases./attempt #263
Plan: aliases already emit from Vault::to_symbol_informations on main. Differentiating by setting container_name on alias symbols to the canonical refname (so Telescope / vim.lsp.buf.workspace_symbol() pickers show where the alias points), skipping blank/duplicate aliases, normalizing nested-note separators, and adding regression coverage for empty-query listing plus alias fuzzy search.
I have submitted a solution for this issue in PR #518. Full implementation and verification included. Payout wallet (Solana):
2BTCUUTviLNDtZDRBhPBTwSXZMrTttPJNbGevMXBBMKK- added a commit that references this issue
on Sep 28, 2026
Right now, only link completion suggests aliases. It would be nice if they were returned by workspace symbols too, e.g. from Telescope or
vim.lsp.buf.workspace_symbol()in Neovim.