Added CLI support for file path input #2
Merged
Conversation
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
- Enabled passing a file path via CLI arguments. - Automatically set the default filter (PSF or MIF) based on the file extension. Intentionally ignored unsupported extensions like psfu, consistent with current behaviors.
Owner
|
Awesome! I reviewed the changes and everything looks fine to me. Thanks! |
Contributor
Author
|
Blazing fast ⚡ feedback! Thank you! 🙏 |
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.
This is a proposal to add support for specifying the file path via CLI.
In my use case, the target file is often located in the current directory or within the Nix store path, which can result in significantly longer paths. Additionally, locating the file from $HOME using the GUI can sometimes feel inconvenient.
To make this workflow smoother, I added an option to specify the file path directly via CLI.
I have tested this change with both absolute and relative paths, and it works as expected.