Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Validator crashes on valid JSON with unexpected shapes

未關閉
#80 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
45/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
python
領域
testing, tooling

研究方向

Start by reading scripts/validate.py and trace how it handles parsed marketplace JSON, plugin entries, and manifest fields. Reproduce the crash with the top-level [] case, then check the listed shape and scalar cases. Done means each invalid input exits with status 1 and identifies the file or field without a traceback; the issue says regression coverage is needed, but tests are excluded by the intake policy.

由索引模型根據 Issue 內容生成。

描述

Problem

python3 scripts/validate.py assumes that parsed JSON values and marketplace plugin entries are objects. Syntactically valid JSON with another shape can therefore terminate with an AttributeError or TypeError instead of reporting a validation error.

Examples include:

  • a top-level array, string, number, or null in marketplace.json;
  • a non-object entry inside marketplace.json.plugins;
  • a top-level non-object value in a plugin manifest;
  • non-string values for fields later passed to regex or path operations.

Expected behavior

The validator should exit with status 1 and identify the invalid file or field, without a Python traceback.

Reproduction

  1. Replace the top-level object in a checkout copy of marketplace.json with [].
  2. Run python3 scripts/validate.py.
  3. The validator reaches object-only operations on the parsed value and crashes.

A complete defensive implementation and regression coverage for arrays, strings, numbers, null, malformed plugin entries, and scalar field mismatches were prepared in #78. The external intake policy does not allow changes to scripts/ or tests/, so that PR is being closed and this issue records the reproducible maintainer-owned fix instead.

主要語言
Python
星號
95
分支
57
PR 合併指標
30 天內沒有已合併 PR

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

zai-org/zcode-plugins 的其他 Issue

查看 zai-org/zcode-plugins 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。