-
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
Add warning for list_files function and related #704
Comments
The Docs currently state:
So I believe we are in sync with the VIP Coding Standards rules for warnings. Thanks for cross-ping! |
@yolih @GaryJones I have a feeling there is some miscommunication going on here. When I read @GaryJones' message, I get the impression he got proper correct file listings, not an empty array. @GaryJones is that correct ? |
Correct. On my VIP test site, the three functions worked as expected. I can get it verified, and if so, or docs need fixing. |
The docs are referring to file listing functions on I've tested and confirmed that the following is true when those functions are used on
I will reopen this issue with the caveat that we should produce a warning indicating that if those functions are being used on a path that points to the |
What problem would the enhancement address for VIP?
I've recently been doing a code review and noticed the
list_files
function had no warning attached. On VIP Filesystem, thelist_files
,scandir
,opendir
will return empty result sets or false, so we should probably highlight this to customers to avoid unexpected results.Describe the solution you'd like
A warning should be added when the following functions are coded:
What code should be reported as a violation?
What code should not be reported as a violation?
Additional context
The text was updated successfully, but these errors were encountered: