-
Notifications
You must be signed in to change notification settings - Fork 45
fix: allow setting MagicDir in Options #337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
56be370
fix: allow setting MagicDir in Options
johnstcn 61029cf
rm unnecessary test
johnstcn 4b3c649
capitalize log line
johnstcn 406bf81
update comment on MagicDir
johnstcn 4d2833f
rename String() to Path()
johnstcn 0f0adc3
use defaultMagicDir for MagicDirectives
johnstcn f7f7049
rm comment
johnstcn 88051f8
make MagicDir un-stringable directly
johnstcn fe05a77
options.MagicDir -> options.MagicDirBase (string)
johnstcn 0b0cdcd
move EmptyWorkspaceDir to options
johnstcn 590155d
move ErrNoFallbackImage to envbuilder package
johnstcn b8eb67e
move MagicDir to internal/magicdir
johnstcn 5726246
correctly set option defaults for magicdir and remote repo dir
johnstcn 552252f
Merge branch 'main' into cj/less-magic
johnstcn File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
make MagicDir un-stringable directly
- Loading branch information
commit 88051f87c3c6c532975bd37c95d7ee7b2167776e
There are no files selected for viewing
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm thinking this abstraction could be a source of bugs. One might not always think to call
String
and instead dostring(MagicDir)
which would result in an empty string or potentially lack of/
.I'd rather see this as a validation step in options so that the input is verified there, and an error can be returned if it's not absolute. The options struct could have the
MagicImage
andMagicBuilt
functions if that's preferable.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think a simpler option here it to simply change the type to a struct with a single unexported field. I'm less worried about leaking the implementation details; we can simply move
MagicDir
to an internal package.