[tools] Add warning for haxelib rebuild with no file found#2028
Merged
joshtynjala merged 2 commits intoopenfl:developfrom Jan 28, 2026
Merged
[tools] Add warning for haxelib rebuild with no file found#2028joshtynjala merged 2 commits intoopenfl:developfrom
joshtynjala merged 2 commits intoopenfl:developfrom
Conversation
This makes it easier to debug when a haxelib name and target name clash.
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
2 participants
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.
Closes #2027
Having it as a warning gives enough information to help with that issue along with the verbose message about it being interpreted as a haxelib. I guess it could also be an error, but not sure if some people rely on being able to just run
lime rebuild <haxelib>for anything, regardless of whether it actually has anything to rebuild or not.