Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Promote standalone component helpers to public API

未关闭
#24,204 1 条评论 5 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
angular, typescript
领域
tooling

调研方向

从提交 e895fc7c1012796442cb7a4a3b9b3a0ec3845b0e 开始,检查从 CDK 移至 schematics 包的独立辅助函数。确定 private 部分如何暴露它们,然后验证这些辅助函数是否被视为 public API;如果该包有相关 coverage,则更新或添加它。

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

描述

area: @schematics/angular
Command

add

Description

With https://github.com/angular/angular-cli/commit/e895fc7c1012796442cb7a4a3b9b3a0ec3845b0e a few standalone helpers were moved from the CDK to the schematics package. I am wondering why they were moved to a "private" section and aren't considered public API. Was this just because standalone components were still in developer preview at that time? Now that angular 15 is going to make standalone components stable could the helpers be moved outside the private section and be treated as public API?

Describe the solution you'd like

With standalone components becoming stable these helpers should become public API as well.

Describe alternatives you've considered

No response

主要语言
TypeScript
星标
27k
派生
11.8k
平均合并
17 小时 25 分钟
30 天内合并 PR
183

贡献指南

打开贡献指南

从这里开始

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

angular/angular-cli 的其他 Issue

查看 angular/angular-cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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