[WIP] More file extensions than .sh and shebang lookup #113
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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 allows more file extensions than just .sh. Besides, we limit the files being analyzed to the ones that have a
bash/shshebang.While doing this, I was able to remove some of the
fs.existsSyncandfs.lstatSynclookups, that would be done directly inglob.I also tried
fast-glob, but the matching algorithm didn't seem that stable (although a lot faster).To support file names without file extensions, we probably need another glob
glob.sync('**/!(*.*)').Related: #47