Add locale support to LSIF dumps

Open
#86 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
devtools

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.

Description

feature-request

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).
Dominant language
TypeScript
Stars
198
Forks
40
Avg merge
3d 7h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/lsif-node

All issues in microsoft/lsif-node

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.