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 天 15 小時
- 30 天內合併 PR
- 50
環境準備
在瀏覽器裡用你自己的 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 則留言 ·
維護者通常 1 天內回覆
-
waiting_for_author
難度 2/5 1-3 小時 新手友好度 78/100
eclipse-score/docs-as-code#1029 · 1 則留言 ·
維護者通常 1 天內回覆
-
intentionally-limited
難度 1/5 1 小時以內 新手友好度 88/100
eclipse-score/docs-as-code#1019 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
eclipse-score/docs-as-code#920 · 2 則留言 ·
維護者通常 1 天內回覆
-
Add project name to headline ...可能重新可做 關聯的 PR 已關閉且未合併。 未關閉documentation
難度 2/5 1-3 小時 新手友好度 68/100
eclipse-score/docs-as-code#613 · 1 則留言 ·
維護者通常 1 天內回覆
查看 eclipse-score/docs-as-code 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 68/100
django-cms/djangocms-frontend#413 ·
-
難度 2/5 1-3 小時 新手友好度 82/100
NanmiCoder/MediaCrawler#1004 ·
-
難度 2/5 1-3 小時 新手友好度 72/100
facebookresearch/xformers#1417 ·
-
question
難度 1/5 1 小時以內 新手友好度 68/100
vllm-project/vime#524 ·
維護者通常 7 天內回覆
-
難度 2/5 1-3 小時 新手友好度 73/100
FinanceFlash/unvibecode#675 ·
維護者通常 1 天內回覆