-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Do we really need readDirectory in runner.js? #172
Comments
There might arise a case surely in the future where we will need to get the files present in the directory. So, I thought of creating a separate function for that. I feel having it this way keeps the code modular. Let me know. For example, check out this. We are calling |
Hey @shalithasuranga, considering this is this issue still up for contributions? |
@shalithasuranga and @Sadaf-A , please do let me know about your suggestions, I will do the needful. |
@shalithasuranga, I analyzed this minor issue and I think was correct. so I raised the PR regarding this thanks |
* refactor: replaced runner.readDirectory by native fs.readdirSync API ( #172 ) * added .vscode in .gitignore, this is for local debugging env
Fixed via #257 .. Thanks 🎉 |
I am not sure why we need to use the existing
readDirectory
function by re-constructing the output offs.readdirSync
. Can we use thefs
API directly in the test file without the wrapper function?Assignee @pathange-s
The text was updated successfully, but these errors were encountered: