Resolve various type errors with New Type Solver - #108
Draft
whoamimaybeme wants to merge 4 commits into
Draft
Conversation
whoamimaybeme
marked this pull request as draft
August 14, 2026 14:13
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 should resolve as many type errors within the New Type Checker as possible without forcing the New Type Checker onto the EToH v6 kit. Since the old type checker is leaving soon, it's probably best to get as many of these issues out of the way before it gets forced.
There will be future pull requests that will come after this one is merged that will resolve the rest of the type errors and will potentially cause a few minor changes to how the v6 kit functions.
A few notes
""andmath.nanas replacements for theUtility.Config.Typetypes. Instances of this include within the MusicZoneEditor and the JumpLauncher.Current changes