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 于 109 天前认领，目前没有进行中的 PR。 未关闭pursuit
purescript/registry-dev#790 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Migrate Pursuit application to the monorepo可能重新可做 @thomashoneyman 于 109 天前认领，目前没有进行中的 PR。 未关闭pursuit
purescript/registry-dev#789 · 1 条评论 · 1 个 reaction · 已指派 1 人 ·
维护者通常 1 天内回复
-
Complete support for monorepos / subdir key and non-GitHub locations可能重新可做 @thomashoneyman 于 109 天前认领，目前没有进行中的 PR。 未关闭
purescript/registry-dev#750 · 1 个 reaction · 已指派 1 人 ·
维护者通常 1 天内回复
查看 purescript/registry-dev 的全部 Issue
相似的 Issue
-
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 天内回复
-
Mend: dependency security vulnerability
难度 2/5 1-3 小时 新手友好度 62/100
ManageIQ/manageiq-pods#1476 ·
维护者通常 1 天内回复
-
mcp: typed tool handlers lose wrapped JSON-RPC errors可能重新可做 关联的 PR 已关闭且未合并。 未关闭
难度 2/5 1-3 小时 新手友好度 85/100
modelcontextprotocol/go-sdk#1529 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
FinanceFlash/unvibecode#818 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100