fix(developer): resolve input project path for kmc copy 🍒 🏠#15703
Merged
mcdurdin merged 1 commit intoMar 9, 2026
Merged
Conversation
User Test ResultsTest specification and instructions User tests are not required Test Artifacts |
kmc copy 🍒kmc copy 🍒 🏠
0194522 to
67c7d84
Compare
8 tasks
Collaborator
|
Changes in this pull request will be available for download in Keyman version 18.0.247 |
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.
Relative paths would cause
kmc copyto fail to find sources files for the project, because component paths would be constructed incorrectly. The cleanest fix is to ensure that we always full resolve local file paths before attempting to copy the project.Fixes: #15659
Cherry-pick-of: #15700
Test-bot: skip