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

[Bug] unknown field ownerlD, expected one of directory, workspaceKey, helperPath, permissions`, `ownerld

Closed Beginner friendly
#1,388 0 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
64/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
backend

Research direction

Start by tracing the Windows MCP startup request from the sender to the receiver’s parameter validation, then find where the ownerID and ownerId field names are defined. Align the mismatched name and verify that clicking “开启 MCP” no longer produces an unknown field error. The issue does not name files or tests, so locate the relevant entry points before making a change.

Written by the indexing model from the issue text.

Description

area:editor bug issue-form:bug P0 platform:windows review: low
Platform / 平台

Windows

Area / 模块

Editor / 编辑器

Lithe version / Lithe 版本

0.6.3

Priority / 优先级

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

OS and architecture / 操作系统与架构

No response

Environment / 环境信息

No response

Steps to reproduce / 复现步骤

No response

Expected behavior / 预期行为

MCP 的内部参数名写错了,发送端和接收端没对齐:

Windows 端发送:ownerID
接收端要求:ownerId
最后一个字母分别是大写 D 和小写 d。接收端严格检查字段,所以点击“开启 MCP”后就拒绝请求,报 unknown field ownerID。

Actual behavior / 实际行为

No response

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

Screenshots or recordings / 截图或录屏
Image
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
12h 54m
Merged PRs (30d)
337

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.