Support package keywords / categories
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
Start by reviewing the existing purs publish registry compatibility code at src/Language/PureScript/Publish/Registry/Compat.hs and the related Pursuit issues 147, 431, and 416. Determine whether the registry should preserve deprecation or arbitrary keywords, then define the accepted metadata and verify that published purs.json packages expose the intended information.
由索引模型根據 Issue 內容生成。
描述
You can currently deprecate packages on Pursuit by setting the keywords field in your bower.json file to contain the keyword pursuit-deprecated. A package with this keyword automatically gets a banner:
The above screenshot shows a deprecated banner because that keyword is set:
Pursuit knows of the keyword because the compiler, in purs publish, will copy the contents of the Bower file into the JSON payload sent to Pursuit. See, for example, the contents of the package upload for a deprecated package here:
Of course, any package published by the registry will use a purs.json file, itself derived from the bowerfile, or the spago.dhall file, or the spago.yaml file. In this case, purs publish will create a Bower package out of the purs.json file, which of course has no keywords field:
The end result is that it is currently impossible to indicate a package is deprecated via the registry. This raises the bigger question: do we want to allow package deprecation?
Package Deprecation and Keywords
A "deprecated" package is really a social category (it's still usable at its published version, of course, but the author is encouraging you not to use it). We may choose to let authors indicate this, or we may not. Advantages of letting a user indicate information like deprecation include:
- For keywords we support, we can display extra information in documentation (such as the deprecation badge)
- For arbitrary keywords, we can support a keyword search on Pursuit
One possible approach is a fixed list of keywords or categories that we know mean something; Crates, for example, has a specific list of categories you can put a package in: https://crates.io/category_slugs
But you can also put arbitrary keywords (up to 5, I believe) in your cargo.toml. We could also support this, allowing people to self-describe with whatever keywords they want.
Related Issues
This has certainly come up before. See:
- 主要語言
- PureScript
- 星號
- 95
- 分支
- 79
- 平均合併
- 16 小時 13 分鐘
- 30 天內合併 PR
- 14
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
purescript/registry-dev 的其他 Issue
-
難度 5/5 一週以上 新手友好度 22/100
purescript/registry-dev#804 · 9 則留言 ·
維護者通常 1 天內回覆
-
A failed publish job permanently blocks retrying the same package version可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉
難度 4/5 3-5 天 新手友好度 48/100
purescript/registry-dev#793 · 5 則留言 ·
維護者通常 1 天內回覆
-
Implement search and versioned Prim docs for the new Pursuit可能重新可做 @thomashoneyman 於 110 天前認領，目前沒有進行中的 PR。 未關閉pursuit
purescript/registry-dev#790 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Migrate Pursuit application to the monorepo可能重新可做 @thomashoneyman 於 110 天前認領，目前沒有進行中的 PR。 未關閉pursuit
purescript/registry-dev#789 · 1 則留言 · 1 個 reaction · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Complete support for monorepos / subdir key and non-GitHub locations可能重新可做 @thomashoneyman 於 110 天前認領，目前沒有進行中的 PR。 未關閉
purescript/registry-dev#750 · 1 個 reaction · 已指派 1 人 ·
維護者通常 1 天內回覆
查看 purescript/registry-dev 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
ROCm/rocm-libraries#15866 ·
維護者通常 2 天內回覆
-
area: web
難度 2/5 1-3 小時 新手友好度 72/100
inabagumi/shinju-date#6823 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
-
ManageSieve proxy: a backend's NO/BYE greeting is skipped as a capability line and reported as EOF未關閉bug
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 82/100
dmtrKovalenko/odiff#191 ·