Enrich prod-errors in Signals with specific problem
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- angular, typescript
- 领域
- backend
调研方向
The report points to packages/core/primitives/signals/src/computed.ts and the computed/linkedSignal error paths; read the cited code and the existing RuntimeError implementation first. Check how production error codes are assigned and surfaced, then define completion as distinguishing these signal errors with useful codes in production while preserving the intended development behavior.
由索引模型根据 Issue 内容生成。
描述
Which @angular/* package(s) are relevant/related to the feature request?
core
Description
Hey team. Currently, errors occurring within computed/linkedSignal lack any information about the nature of the error itself in the prod: https://github.com/angular/angular/blob/92e5aa8f154096a756757d0e295cde4299788650/packages/core/primitives/signals/src/computed.ts#L136
As a result, the error signature in Sentry is uninformative, making it impossible to determine where an error originated without examining the stack traces:
Furthermore, when errors arise from different locations (for instance, from computed and linkedSignal) it becomes difficult to distinguish between them in Sentry’s error lists (though Sentry’s built-in grouping mechanism does at least separate them), which complicates the process of locating and debugging errors.
Proposed solution
For each error, add a code instead of a message, as has already been done for RuntimeError
Alternatives considered
I know why it has been done, but maybe it is possible to simplify (shorten) error messages in all modes and remove the ngDevMode at all.
- 主要语言
- TypeScript
- 星标
- 101k
- 派生
- 28.2k
- 平均合并
- 2 天 45 分钟
- 30 天内合并 PR
- 373
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
angular/angular 的其他 Issue
-
Two-way binding documentation is missing important information可能重新可做 关联的 PR 已关闭且未合并。 未关闭area: docs
难度 2/5 1-3 小时 新手友好度 75/100
angular/angular#71796 · 2 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
area: core
难度 2/5 1-3 小时 新手友好度 78/100
angular/angular#71585 · 3 条评论 ·
维护者通常 1 天内回复
-
Assigning to a template reference in an event binding isn't reported by the compiler可能重新可做 关联的 PR 已关闭且未合并。 未关闭area: compiler
难度 2/5 1-3 小时 新手友好度 74/100
angular/angular#71511 · 3 条评论 ·
维护者通常 1 天内回复
-
Signal Forms: `validateStandardSchema` throws a TypeError for an issue whose path runs through a key the model lacks可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭area: forms gemini-triaged
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
`Symbol.iterator in FieldTree` is always false可能重新可做 关联的 PR 已关闭且未合并。 未关闭area: forms forms: signals
难度 2/5 1-3 小时 新手友好度 78/100
angular/angular#70252 · 3 条评论 ·
维护者通常 1 天内回复
相似的 Issue
-
truapi-release
难度 2/5 1-3 小时 新手友好度 72/100
paritytech/product-sdk#529 ·
维护者通常 1 天内回复
-
Environments table lists page size 5 after 30可能已有人在做 @raus7n 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 90/100
litmuschaos/litmus#5743 ·
维护者通常 2 天内回复
-
desktop grp:admin-donors type:graphics-bug ui-admin
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
milind-soni/OpenMausBot#6730 ·
维护者通常 1 天内回复
-
Status: Triage Type: Bug / Error
难度 2/5 1-3 小时 新手友好度 69/100
mermaid-js/mermaid-v13#1059 ·
维护者通常 1 天内回复