Repository navigation
test: build the expected message template path with the platform separator - #35
Merged
Merged
Conversation
…rator The expectation was hand-built with a hard-coded "/", while the source emits `__DIR__` (native separator) followed by the literal. The two only agreed on POSIX, so the test failed on Windows even though the path was correct. Signed-off-by: Joey Smith <jsmith@webinertia.net> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
The expectation was hand-built with a hard-coded "/", while the source emits
__DIR__(native separator) followed by the literal. The two only agreed on POSIX, so the test failed on Windows even though the path was correct.No source change: the paths themselves are valid on both platforms, only the expectation was platform-specific.
Verified against the pinned Mago (
1.51.2):format --check,lint,analyzeandguardall exit 0, and the affected unit tests pass.