-
Notifications
You must be signed in to change notification settings - Fork 40
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
fix: ignoring symlinks #528
base: main
Are you sure you want to change the base?
Conversation
@brianmcgee : I have question to the test here: Why do we even test to run in the Line 1401 in bdd8687
|
5555359
to
20fea9d
Compare
In that particular test, it's checking that if we momentarily switch to the filesystem walker, the |
Ah ok. I need to still refactor the symlink resolving code in the Run function, its not good yet. I think the only correct way is to us EvalSymlinks/ or only os.Stat and check for errors and make the test pass. As this is only done on path inputs it should not degrade performance. ki |
@brianmcgee: The thins is done. Happy for a review what you think about the behavior. Hope its ok like that. |
Thanks for this, I'll try and review it in the next few days. |
@gabyx please rebase on latest |
Co-authored-by: Brian McGee <[email protected]>
Co-authored-by: Brian McGee <[email protected]>
237342a
to
dfeda94
Compare
@brianmcgee: Did the changes and rebased. |
Thanks 🙏 I'll give it another review in the next day or so |
@brianmcgee : I tried the following:
Run
functions to pass the resolved paths to the readers, such that the readersFilesystem
orGit
can ignore symlinks always.treefmt symlink.yaml
ortreefmt /a-symlink/b/c/d.yaml
should be allowed.See some comments I need help on which is unclear to me.
Fixes: #495