‹ 首页

cli-compile-surface-hardening

@fritzandfriends · 收录于 昨天 · 上游提交 1 个月前

Keep migrated Blazor output compiling when more Web Forms artifacts stay on the generated compile surface

场景代码迁移编译修复

适合你，如果正在将 Web Forms 迁移到 Blazor 并遇到编译错误

/ 下载安装
https://github.com/fritzandfriends/blazorwebformscomponents/tree/dev/.squad/skills/cli-compile-surface-hardening ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add fritzandfriends/blazorwebformscomponents/cli-compile-surface-hardening
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- fritzandfriends/blazorwebformscomponents/cli-compile-surface-hardening
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify fritzandfriends/blazorwebformscomponents/cli-compile-surface-hardening
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
449GitHub stars
~448上下文体积 · 单文件
索引托管

怎么用

技能原文 SKILL.md作者撰写 · MIT · 3154758
Context

Use this when the migration CLI starts emitting more generated .razor.cs files or copying more legacy source into the output project. The goal is to preserve deterministic L1 behavior while preventing compile failures from style analyzers, generic Razor component inference, or unresolved markup references.

Patterns
  • In generated migration projects, prefer <EnforceCodeStyleInBuild>false</EnforceCodeStyleInBuild> over broad warning suppression when copied legacy files would otherwise fail repo-level IDE analyzers.
  • Add validator generic arguments with the BWFC component's actual generic parameter name, not an assumed TValue alias:
  • RequiredFieldValidator → Type="string"
  • CompareValidator / RangeValidator → InputType="string"
  • Run markup-driven member stub generation after the main code-behind transforms, using transformed Razor markup (metadata.MarkupContent) as the source of truth.
  • Stub only the deterministic missing-member shapes that are safe to infer mechanically:
  • @MethodName() → render-method stub returning object?
  • @_fieldName → private object? field
  • OnClick="@HandlerName" and similar → void HandlerName(object? sender, EventArgs e)
  • Register new transforms in both production DI (src\BlazorWebFormsComponents.Cli\Program.cs) and tests\BlazorWebFormsComponents.Cli.Tests\TestHelpers.cs so the lightweight and full pipelines stay aligned.
Examples
  • src\BlazorWebFormsComponents.Cli\Transforms\Markup\ValidatorGenericTypeTransform.cs
  • src\BlazorWebFormsComponents.Cli\Transforms\CodeBehind\MarkupReferencedMemberStubTransform.cs
  • tests\BlazorWebFormsComponents.Cli.Tests\TransformUnit\CompiledCodeBehindStubPipelineTests.cs
Anti-Patterns
  • Suppressing all warnings/errors in the generated project when only code-style analyzers are the problem.
  • Injecting TValue="string" into BWFC validators that actually expose Type or InputType generic parameters.
  • Generating markup-reference stubs before markup transforms run, or reading original Web Forms markup instead of the transformed Razor output.
  • Emitting placeholder stubs for every @Identifier token; restrict deterministic generation to the specific reference shapes you can classify safely.
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…