Add support for debugging cyclic wisps with HexDebug #188
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
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.
This PR adds optional support for HexDebug's new debug environment API.
Cyclic wisps will automatically be created in debug mode if all of the following conditions are met:
To simplify the implementation, HexDebug Core will be bundled in Hexal via Jar-in-Jar. This means anything from the
gay.object.hexdebug.core.apipackage can be safely accessed without first checking if HexDebug is loaded or not.To allow running the dev environment with HexDebug present, it was also necessary to bump the minimum required versions of Kotlin, Fabric Loom, Fabric Loader, Fabric Language Kotlin, Kotlin For Forge, and MixinExtras.