Reject deprecated Needs inventory inputs in docs(data)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start at the public macro boundary in docs.bzl and read the deprecation documented in #897; locate the consumers and fixtures that pass inventory labels through data. Migrate those inputs to external_needs, then trace the interactive build and Needs export paths to identify the implicit imports to remove. Done means inventory labels in data are rejected with a diagnostic, explicit imports and ordinary data files still work, and the API and migration docs plus coverage are updated.
由索引模型根据 Issue 内容生成。
描述
Needs inventories should be imported explicitly through docs(external_needs = [...]). Passing inventory targets through docs(data = [...]) is deprecated but still accepted, leaving two routes for the same dependency and retaining compatibility plumbing.
The deprecation is documented in #897 and reported at the public macro boundary in docs.bzl. Remove this compatibility route in a breaking release.
Acceptance criteria:
- Migrate remaining consumers and fixtures from inventory labels in
datatoexternal_needs. - Reject recognized Needs inventory labels in
docs(data = [...])with a clear diagnostic pointing toexternal_needs. - Remove the implicit inventory import from
datain both interactive builds and Needs export actions. - Preserve ordinary supporting/runtime
datafiles and existing supportedexternal_needsinputs. - Cover the rejection and successful explicit import, and update the API and migration documentation.
Keep the scope limited to the deprecated data route. Removing the legacy needs_json label from explicit external_needs is a separate decision. Removing bundle data mounts is also a separate change.
- 主要语言
- Python
- 星标
- 11
- 派生
- 39
- 平均合并
- 1 天 13 小时
- 30 天内合并 PR
- 46
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
eclipse-score/docs-as-code 的其他 Issue
-
bug
难度 1/5 1 小时以内 新手友好度 82/100
eclipse-score/docs-as-code#1031 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
eclipse-score/docs-as-code#1029 ·
维护者通常 1 天内回复
-
intentionally-limited
难度 1/5 1 小时以内 新手友好度 88/100
eclipse-score/docs-as-code#1019 ·
维护者通常 1 天内回复
-
Graph-check unit tests fail under direct pytest because logger fixtures assume Bazel runfiles可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭bug
难度 2/5 1-3 小时 新手友好度 78/100
eclipse-score/docs-as-code#999 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
eclipse-score/docs-as-code#920 · 2 条评论 ·
维护者通常 1 天内回复
查看 eclipse-score/docs-as-code 的全部 Issue
相似的 Issue
-
cli good first issue help wanted python up-for-grabs
难度 2/5 1-3 小时 新手友好度 75/100
andrewsiah/agentswarm-data-tasks#36 ·
维护者通常 1 天内回复
-
bug drawing-tools
难度 2/5 1-3 小时 新手友好度 76/100
cofade/open-garden-planner#827 ·
维护者通常 1 天内回复
-
Methodology page未关闭documentation site texts
难度 2/5 1-3 小时 新手友好度 67/100
Krasnopjorovs/temet#66 ·
-
bug
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复