microsoft / microsoft/lsif-node
Add locale support to LSIF dumps
Open
Nobody has claimed this yet.
feature-request
- Dominant language
- TypeScript
- Stars
- 198
- Forks
- 40
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 1
Description
Modern tools localize thinks like hovers, JS docs to compiler diagnostics. The LSIF graph should have support for:
- knowing for which locale it got generated
- store UI strings in n locale formats
- separate the UI strings from the graph so that locale specific strings can be merged into a graph later on (even if we have to run the tool 2 times).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing how LSIF dumps currently represent graph metadata and UI strings; define the locale metadata, separate locale-specific strings, and later merge behavior, then add coverage for generation and merging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100