Resolve path options against the project directory - #26
Merged
Merged
Conversation
A relative --gradle-path or --pbxproj-path was resolved against the working directory, so combining either with --project-dir pointed at the wrong project unless the path was absolute. Both are now resolved against the project directory, which is the working directory when --project-dir is not given, so plain invocations behave as before.
friederbluemle
force-pushed
the
path-options
branch
from
September 4, 2026 06:34
5bacb89 to
cde7fe1
Compare
Contributor
|
🎉 Released in v0.7.0 |
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
1 participant
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.
A relative
--gradle-pathor--pbxproj-pathwas resolved against the working directory, so combining either with--project-dirpointed at the wrong project unless the path was absolute. Both are now resolved against the project directory. Without--project-dirthat is the working directory, so plain invocations behave as before, and absolute paths are unaffected.The CLI test that pinned the old behavior flips to cover the new one for both flags, the
--helptext says what the paths are relative to, and the README notes it below the options table.