[FEATURE]: Dictionary of all crates

未关闭
#87 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
rust
领域
cli, tooling

调研方向

Start by reading the LS CLI command structure and how it loads or updates dictionaries; the issue does not name files or tests. Explore Cargo's local registry index and cache, plus Cargo.lock as a possible input, then decide how private registries, name synonyms, and configurable automatic updates should work. Done means users can build or update a local crate name dictionary from a chosen source.

由索引模型根据 Issue 内容生成。

描述

enhancement
Feature Description

Could be great to have dictionary of all crate names published on crates.io, with synonyms like "foo_bar" for "foo-bar" or "foo-bar-rs" and vice versa.

Use Case

Automatically all used package names are in the allow-list. Useful for package manifests like Cargo.toml as well as entire codebase.

Proposed Solution

New command in LS CLI to build or update dictionary using existing cargo' index (which in the ~/.cargo/registry/index) or maybe cache 🤷🏻‍♂️

Also probably update that dictionary automagically, but it should be configurable.

Alternative Solutions

Builtin or downloadable dictionary.

Examples

No response

Additional Context

I suppose better way is to give to user a way to index some registry (such as cargo index, or cargo cache, or just Cargo.lock) and so to build his personal local dictionary. This way supports any private registries and private crates.

主要语言
Rust
星标
925
派生
59
平均合并
53 分钟
30 天内合并 PR
10

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

blopker/codebook 的其他 Issue

查看 blopker/codebook 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。