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

[Bug] 编辑界面打开多个文件后展示的效果是多文件并排拆分的展示效果,没办法打开文件全占编辑窗口;如果是 多模块的大项目 就会导致 重复的 各种启动名称;并且如果是关闭窗口操作,关闭后也没有将已经启动的服务给关闭掉,导致启动的服务成为了遗留进程。

Open
#798 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
typescript
Domain
desktop

Research direction

Start with the TypeScript editor file-opening flow described in the reproduction steps, then trace the close-window path and the service lifecycle. Reproduce the issue on Windows 11 with two files and a multi-module project. Done means files no longer open in an unwanted split view, duplicate startup names are avoided, and closing the window stops services it started.

Written by the indexing model from the issue text.

Description

area:editor bug P1 platform:windows review: low
Platform / 平台

Windows

Area / 模块

Editor / 编辑器

Lithe version / Lithe 版本

0.5.1

Priority / 优先级

P1 / 尽快处理:使用体验大幅下降,但通常仍可继续使用

OS and architecture / 操作系统与架构

windows11

Environment / 环境信息

No response

Steps to reproduce / 复现步骤

项目树上打开一个文件后,再双击另一个文件打开就会看到文件内容在编辑界面并排展示

Image
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.