You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LSP has a feature called "document symbol" where all symbols in a document are returned as a hierarchy, including their spans. Then, the current hierarchy is shown at the top of the editor, and you can jump to any symbol in the hierarchy by doing command+o (on a Mac). It would be nice if it worked the same way in Noir.
Happy Case
LSP document symbol is implemented.
Project Impact
None
Impact Context
No response
Workaround
None
Workaround Description
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
Yes
Support Needs
No response
The text was updated successfully, but these errors were encountered:
# Description
## Problem
Resolves#5533
## Summary
With this you can see where you are at any time, and jump to any symbol
in the document.
https://github.com/user-attachments/assets/74ebdb36-cd51-4afc-a33e-775156c1317b
## Additional Context
None
## Documentation
Check one:
- [x] No documentation needed.
- [ ] Documentation included in this PR.
- [ ] **[For Experimental Features]** Documentation to be submitted in a
separate PR.
# PR Checklist
- [x] I have tested the changes locally.
- [ ] I have formatted the changes with [Prettier](https://prettier.io/)
and/or `cargo fmt` on default settings.
Problem
LSP has a feature called "document symbol" where all symbols in a document are returned as a hierarchy, including their spans. Then, the current hierarchy is shown at the top of the editor, and you can jump to any symbol in the hierarchy by doing command+o (on a Mac). It would be nice if it worked the same way in Noir.
Happy Case
LSP document symbol is implemented.
Project Impact
None
Impact Context
No response
Workaround
None
Workaround Description
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
Yes
Support Needs
No response
The text was updated successfully, but these errors were encountered: