eclipse-theia/theia

improve license detection for built-in extensions

Open

#7,381 建立於 2020年3月20日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)TypeScript (18,676 star) (2,478 fork)batch import
enhancementhelp wantedvscodevsx-registry

描述

Currently we always try to look into LICENSE file, but there can be more locations including configurable.

Form @spoenemann:

  • If a package.json has SEE LICENSE IN ..., then try there first
  • after that try LICENSE.md, LICENSE, and LICENCE.txt in this order

貢獻者指南

技術棧
typescriptnodejsjavascript
領域
backendtooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
TypeScriptNode.js file systemJSON parsing
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
75
研究方向
Start by finding the current license detection logic, likely in a file related to extension metadata or packaging. Modify it to first check package.json for a 'SEE LICENSE IN' directive, then attempt to read LICENSE.md, LICENSE, and LICENCE.txt in order. Ensure tests are added to cover each case.
improve license detection for built-in extensions · eclipse-theia/theia#7381 | Good First Issue