-
-
Notifications
You must be signed in to change notification settings - Fork 0
Tour Operator plugin to meet WordPress Coding Standards before pushing 2.0 release to wordpress.org #358
Copy link
Copy link
Labels
status:needs-devEarly execution signal (triage queue for engineering)Early execution signal (triage queue for engineering)status:needs-more-infoMissing details to proceedMissing details to proceed
Milestone
Description
Ensure Tour Operator Plugin Meets WordPress Coding Standards
Issue Summary
Before we push the upcoming 2.0 release of the Tour Operator plugin to WordPress.org, we need to ensure the entire codebase adheres to WordPress Coding Standards.
Steps to be Completed:
- Run Plugin Check: Use the Plugin Check Plugin to verify compliance with WordPress.org guidelines.
- Run PHPCS: Use PHP_CodeSniffer with the WordPress Coding Standards to identify any code violations.
- Command:
phpcs --standard=WordPress .
- Command:
- Resolve PHPCS Violations: Address flagged issues while maintaining functionality.
- Check JavaScript Standards: Ensure all JavaScript files comply with WordPress JavaScript Coding Standards.
- Command:
eslint --config=eslint-config-wordpress .
- Command:
- Update Documentation: Ensure proper inline documentation in accordance with WordPress PHP Documentation Standards.
- Final Review: Perform a final code review to confirm readiness for the
2.0release.
Acceptance Criteria:
- Plugin passes all Plugin Check and coding standard checks.
- No PHPCS or ESLint errors.
- All documentation adheres to standards.
- Plugin is ready for submission to WordPress.org.
Related Links:
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
status:needs-devEarly execution signal (triage queue for engineering)Early execution signal (triage queue for engineering)status:needs-more-infoMissing details to proceedMissing details to proceed
Type
Projects
Status
📥 Needs Dev