Resource generation changes committed wrappers during a clean build
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- node.js, typescript
- 领域
- build-system
调研方向
Read gulp/Resource.template.ts and inspect the buildApp path through @storage-explorer/build-common/gulp/resourceGenerator; compare the generated wrappers under src/Standalone/app/resources with baseline 9a2a48373039fc743ca6eacf6459438c4af8f277. Trace the formatting step and determine why the normal build may not leave these changes. Done means regeneration is stable and the reason for the differing build behavior is established.
由索引模型根据 Issue 内容生成。
描述
Problem
Building Storage Explorer regenerates tracked resource wrappers with a blank line that is absent from the committed files. This makes an otherwise clean checkout dirty and caused orchestrator setup checks to block unrelated bug fixes.
Evidence
- Observed product baseline:
9a2a48373039fc743ca6eacf6459438c4af8f277. - Standalone declares
@storage-explorer/build-common^1.5.0; its lockfile and installed package both resolve to1.5.0. buildApprunsbuildResources, which uses@storage-explorer/build-common/gulp/resourceGeneratorand writes tosrc/Standalone/app/resources.gulp/Resource.template.tsincludes a blank line between the missing-resource-manager guard and the return statement in#getResource. The committed versions of 25 wrappers lack that line.- Running the generator transforms in memory produced 27 outputs matching the affected worktree files exactly; 25 differ from the committed baseline by one added blank line each. No product build was rerun for this comparison.
- Current build-common source, version
1.5.5, still contains the blank line. History traces its addition to the March 2025 ESLint migration (0681eb760ac13a01999547a8c0a40c0821352763). Published newer package contents were not verified because registry authentication failed.
Expected behavior
A clean build should leave committed generated wrappers unchanged when their inputs and locked dependencies have not changed.
Requested resolution
Reconcile the committed wrappers and generator/formatting pipeline so regeneration is stable. Determine whether generated files should be refreshed or a subsequent formatting step is inconsistent; do not assume removing the template's blank line is the correct fix. Also establish why the user's normal build does not appear to leave these changes.
Impact
Seven independent orchestrator work items were blocked during setup by identical generated-file changes, before fix implementation. The orchestrator is being adjusted separately to allow recognized generated build outputs while retaining source/test and Git-state protections.
- 主要语言
- 没有语言数据
- 星标
- 458
- 派生
- 92
- 平均合并
- 17 小时 57 分钟
- 30 天内合并 PR
- 4
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoft/AzureStorageExplorer 的其他 Issue
-
难度 2/5 1-2 天 新手友好度 76/100
microsoft/AzureStorageExplorer#9186 ·
-
:globe_with_meridians: hard-coded string :globe_with_meridians: localization :test_tube: testing
难度 2/5 1-3 小时 新手友好度 68/100
microsoft/AzureStorageExplorer#9152 ·
-
难度 4/5 3-5 天 新手友好度 52/100
microsoft/AzureStorageExplorer#9235 ·
-
难度 4/5 3-5 天 新手友好度 22/100
microsoft/AzureStorageExplorer#9233 ·
-
难度 3/5 1-2 天 新手友好度 42/100
microsoft/AzureStorageExplorer#9232 ·
查看 microsoft/AzureStorageExplorer 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
chore good first issue priority: low size: XS status: needs triage
难度 2/5 1-3 小时 新手友好度 86/100
cubrid-lab/sqlalchemy-cubrid#1293 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
ci enhancement need-triage
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复