Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate FrameworkType and FrameworkField to XPoet. #4538

Merged
merged 1 commit into from
Dec 18, 2024

Conversation

copybara-service[bot]
Copy link

Migrate FrameworkType and FrameworkField to XPoet.

This CL:

  • Migrates FrameworkField to XPoet
  • Migrates FrameworkType to XPoet
  • Adds XTypeNames -- a version of TypeNames compatible with XPoet.
  • Adds legacy toJavaPoet() calls where needed. These will be cleaned up in future CLs as we migrate the corresponding usages to use XPoet.

#dagger-xpoet-migration

RELNOTES=N/A

This CL:

  * Migrates `FrameworkField` to XPoet
  * Migrates `FrameworkType` to XPoet
  * Adds `XTypeNames` -- a version of `TypeNames` compatible with XPoet.
  * Adds legacy `toJavaPoet()` calls where needed. These will be cleaned up in future CLs as we migrate the corresponding usages to use XPoet.

#dagger-xpoet-migration

RELNOTES=N/A
PiperOrigin-RevId: 707570301
@copybara-service copybara-service bot merged commit 6ee6092 into master Dec 18, 2024
1 check passed
@copybara-service copybara-service bot deleted the test_697774243 branch December 18, 2024 17:07
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.

1 participant