clj-python / clj-python/libpython-clj
py. syntax is doing weird things with the clj-kondo linter
還沒有人認領這個 Issue。
- 主要語言
- Clojure
- 星號
- 1.2k
- 分支
- 74
- PR 合併指標
- 30 天內沒有已合併 PR
描述
The linter is doing something weird, because it assumes that py/py. is actually a reference to the symbol "py/py" with no ".".
I'm unable to write a custom :lint-as for this, because clj-kondo doesn't consider the possibility that "py." could represent a macro. ingoring :unresolved-var doesn't quite fill my usecase, as I want to remove the red squiglies under the second argument of the py. call as well.
I think clj-kondo is technically in the right here, because py. isn't supported clojure syntax, although I do like the py. notation, and it'd be nice if it was supported. I don't ask to change the notation, but it'd be nice to have a workaround that fixes these tooling issues.
https://clojure.org/reference/reader#_reader_forms
Symbols beginning or ending with '.' are reserved by Clojure.
Great Library! -- Sammy
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
首先使用 clj-kondo 重現 py/py. 呼叫,並比較自訂 :lint-as 的行為與抑制 :unresolved-var 的效果。沒有指定實作檔案或測試;追蹤 clj-kondo 如何解析保留的 py. 表示法,並將完成定義為一個可運作的 lint 設定或有文件記載的支援,能移除回報的兩個波浪線標記。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- clojure, python
- 領域
- tooling
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 25/100