-
Notifications
You must be signed in to change notification settings - Fork 2k
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: search file by supported extension use manually specific config … #1840
base: master
Are you sure you want to change the base?
Conversation
👋 Thanks for contributing to Viper! You are awesome! 🎉 A maintainer will take a look at your pull request shortly. 👀 In the meantime: We are working on Viper v2 and we would love to hear your thoughts about what you like or don't like about Viper, so we can improve or fix those issues. ⏰ If you have a couple minutes, please take some time and share your thoughts: https://forms.gle/R6faU74qPRPAzchZ9 📣 If you've already given us your feedback, you can still help by spreading the news, https://twitter.com/sagikazarmark/status/1306904078967074816 Thank you! ❤️ |
could you review it @sagikazarmark
|
Although I see the value in this change, I'm afraid it would create more confusion later on. I'm working on #1849 right now. I hope it will help people make configuration searching easier. |
#1849 is perfer good design, BUT the orginal function of
why not let it work as expectly? it's now works in some way, like if no other supported file name exist in the current file path. em... , I think it's more confused to maintain this issue of this function. SO, I want to 2 points:
|
So when you say it's the expected functionality, it's not exactly true, although I understand why people would expect that. I don't have an exact example that would break, but given the complexity (and past experiences) it could easily break for someone out there. Then what? Let me think about it. But right now, I'd prefer deprecating the old API and drive people towards the new one. |
this PR is aimed to resolve issue #1754 and #1401, with compatible changes about
searchInPath
test all imaginable situation passed and statement coverage is 100%: