Skip to content

feat(cli): compile page code-behind safely#545

Open
csharpfritz wants to merge 1 commit intoFritzAndFriends:devfrom
csharpfritz:feature/wingtip-next-features-review
Open

feat(cli): compile page code-behind safely#545
csharpfritz wants to merge 1 commit intoFritzAndFriends:devfrom
csharpfritz:feature/wingtip-next-features-review

Conversation

@csharpfritz
Copy link
Copy Markdown
Collaborator

Summary

  • merge the page runtime shim so \Page\ reuses \WebFormsPageBase\ and \WebFormsPage\ composes the shared head renderer
  • emit compile-safe page code-behind into the generated app while quarantining pages that still contain unsupported Web Forms patterns
  • add explicit BWFC global usings to scaffolded \GlobalUsings.cs\ so local project-reference migrations compile emitted .razor.cs\ files correctly
  • update focused CLI tests and refresh the page/runtime docs
  • capture Wingtip benchmark progression in
    un29,
    un30, and
    un31\ reports

Validation

  • focused CLI tests for scaffolding, pipeline integration, and semantic pattern catalog
  • fresh Wingtip migration benchmarks recorded under \dev-docs/migration-tests/wingtiptoys/run29,
    un30, and
    un31\

Wingtip impact

  • run30 reduced the fresh Wingtip build from 183 errors to 60 by enabling compile-safe page code-behind emission
  • run31 validated the imports fix by collapsing the deduplicated page-type import bucket (\CS0246) from 41 to 7 and exposing the next support-code/semantic failure layers

Merge the page runtime shim, emit compile-safe page code-behind into the generated app, and add explicit BWFC global usings for local project-reference scaffolds. Include focused test updates plus Wingtip run29-run31 reports documenting the benchmark progression.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Comment on lines +354 to +356
}
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants