posit-dev / posit-dev/positron
Track whether a language runtime has a supported version
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 206
Description
In https://github.com/posit-dev/positron/pull/6934 we added some visual indicators to Python interpreters that have unsupported versions. In particular, we prepend Unsupported: to the runtimeName. This shows up whenever the full name is used.
For Python, it's technically okay for someone to use an unsupported version; there's just a chance that something won't work. So we warn the user but let them activate it anyway, just in case it's their best option.
However,
- this sometimes adds some visual clutter; if a user is using an unsupported version, the
Unsupported:tag appears in the Console, Variables pane, etc. If they've gotten to that point, they probably don't care. - this perhaps isn't visually distinct enough in the "select session" dropdown. We'd like to use an Octicon or something, but that doesn't work in the Console.
It would be nice if different UI elements could decide how to display an unsupported version differently. We could track whether it's unsupported in LanguageRuntimeMetadata.
This could be language agnostic (though arguably less useful for R).
Contributor guide
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
Start by reviewing pull request 6934 and locating the LanguageRuntimeMetadata definition and its consumers. Trace where runtimeName is displayed, especially the Console, Variables pane, and session-selection dropdown. Done means unsupported status is available as separate metadata so each UI element can choose its own presentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100