BridgeJS: Migrate to IntrinsicJSFragment for enums #441
+672
−514
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
krodak
changed the title
kateinoigakukun
approved these changes
Sep 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduction
Moving most of the code related to generate helper functions for custom lower / raise of associated values in enums to dedicated
IntrinsicJSFragmentand moving toCodeFragmentPrinterinstead of "manual" code generation management.Similar update done for
simple,rawtype enums and namespaces.Notes
I've also started migrating some code from
BridgeJSLinkto use fragment printer, but I'll post another PR for clarity, as it's not related to enums and I'd rather keep PRs smaller when possible (which is harder to do when adding new functionality with tests)