We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With coding standards implemented and linting on the way, it is to be considered if this library should apply all WordPress coding standards.
Some of the prompts to consider:
phpcs: File operations should use WP_Filesystem methods instead of direct PHP filesystem calls.
(This library has no direct access to WordPress. And for good reason.)
phpcs: Missing doc comment for function testUnzipFileWhenUsingAbsolutePath()
(Expects docs for every test.)
phpcs: Missing short description in doc comment
(Expects description for every doc.)
phpcs: Missing @throws tag in function comment
… and more.
The text was updated successfully, but these errors were encountered:
@throws
This one sounds useful, the rest I'd disable for now. Good call. Let's pick and choose the rules that are the most useful and fine-tune them as we go.
Sorry, something went wrong.
No branches or pull requests
With coding standards implemented and linting on the way, it is to be considered if this library should apply all WordPress coding standards.
Some of the prompts to consider:
(This library has no direct access to WordPress. And for good reason.)
(Expects docs for every test.)
(Expects description for every doc.)
… and more.
The text was updated successfully, but these errors were encountered: