Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]项目是jdk6,为什么设置中还显示其他版本,设置是跟项目来的还是全局

Open Beginner friendly
#1,118 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
java, typescript
Domain
tooling

Research direction

The issue concerns JDK version display in IDE settings when a project specifies a particular JDK. Start by locating the settings UI code for JDK configuration and the project model that stores the JDK version. Trace how the settings are populated—likely involving environment variable scanning—and identify where the project's JDK version should take precedence. 'Done' means the settings correctly show only the project's JDK version (e.g., JDK6) instead of all detected versions.

Written by the indexing model from the issue text.

Description

area:editor bug P0 platform:macos review: low
Platform / 平台

macOS

Area / 模块

Editor / 编辑器

Lithe version / Lithe 版本

0.6.0

Priority / 优先级

P0 / 立即处理:已严重影响使用体验,核心流程受阻或无法正常使用

OS and architecture / 操作系统与架构

No response

Environment / 环境信息
Image
Steps to reproduce / 复现步骤

设置了JDK,每次打开都会按照环境变量进行匹配

Expected behavior / 预期行为

No response

Actual behavior / 实际行为

No response

Logs or diagnostic output / 日志或诊断输出

Screenshots or recordings / 截图或录屏

No response

Checklist / 提交前检查
  • I searched existing issues for duplicates. / 我已搜索现有 Issue,确认没有重复报告。
  • I removed secrets and personal data from the report. / 我已从报告中移除敏感信息和个人数据。
Dominant language
TypeScript
Stars
1.8k
Forks
151
Avg merge
7h 51m
Merged PRs (30d)
351

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 1lck/Lithe-IDEA

All issues in 1lck/Lithe-IDEA

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.