Refactor

Author: PDowney

.github/CODE_OF_CONDUCT.md

@@ -54,4 +54,4 @@ respond in a way that they deem appropriate to the circumstances.
 
 This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org),
 version 2.1, available at
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).

.github/ISSUE_TEMPLATE/compatibility-test-failure.md

@@ -19,14 +19,14 @@ The automated compatibility test for PHP {{ env.PHP_VERSION }} has failed.
 
 ### Next Steps
 
-This issue has been automatically created because the Optimizations ACE MC plugin failed to load properly with PHP {{ env.PHP_VERSION }}. This could indicate compatibility issues that need to be addressed.
+This issue was automatically created because the Optimizations ACE MC plugin failed to load properly with PHP {{ env.PHP_VERSION }}. This could indicate compatibility issues that need attention.
 
-#### Recommended Actions:
+#### Recommended Actions
 
-1. Review the workflow logs for specific error messages
-2. Check for PHP {{ env.PHP_VERSION }} specific syntax or function compatibility issues
-3. Test locally with PHP {{ env.PHP_VERSION }} to reproduce the issue
-4. Make necessary code updates to ensure compatibility
+1. Review the workflow logs for specific error messages.
+2. Check for syntax or function compatibility issues specific to PHP {{ env.PHP_VERSION }}.
+3. Test with PHP {{ env.PHP_VERSION }} to reproduce the issue.
+4. Make the code updates needed to ensure compatibility.
 
 Once fixed, please close this issue and reference it in the changelog.
 

.github/ISSUE_TEMPLATE/phpcs-failure.md

@@ -11,20 +11,24 @@ assignees: []
 The PHPCS (PHP CodeSniffer) check has failed for the repository.
 
 **Failure Details:**
+
 - **PHP Version:** {{ env.PHP_VERSION }}
 - **Workflow Run:** [View Details]({{ env.WORKFLOW_URL }})
 - **Run ID:** {{ env.RUN_ID }}
 
 **What happened:**
+
 The code does not meet WordPress coding standards as defined by PHPCS.
 
 **What needs to be done:**
-1. Review the PHPCS output in the failed workflow run
-2. Fix coding standard violations in the code
-3. Ensure all PHP files follow WordPress coding standards
-4. Test locally with: `phpcs --standard=WordPress --extensions=php .`
+
+1. Review the PHPCS output in the failed workflow run.
+2. Fix coding standard violations in the code.
+3. Ensure all PHP files follow WordPress coding standards.
+4. Test with: `phpcs --standard=WordPress --extensions=php .`
 
 **Resources:**
+
 - [WordPress Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/)
 - [PHP CodeSniffer Documentation](https://github.com/squizlabs/PHP_CodeSniffer)
 

.github/ISSUE_TEMPLATE/phpmd-failure.md

@@ -11,24 +11,28 @@ assignees: []
 The PHPMD (PHP Mess Detector) check has failed for the repository.
 
 **Failure Details:**
+
 - **PHP Version:** {{ env.PHP_VERSION }}
 - **Workflow Run:** [View Details]({{ env.WORKFLOW_URL }})
 - **Run ID:** {{ env.RUN_ID }}
 
 **What happened:**
+
 The code has quality issues detected by PHPMD analysis.
 
 **What needs to be done:**
-1. Review the PHPMD output in the failed workflow run
+
+1. Review the PHPMD output in the failed workflow run.
 2. Address code quality issues such as:
    - Complex methods that should be simplified
    - Unused variables or parameters
    - Code duplication
    - Naming conventions
    - Design issues
-3. Test locally with: `phpmd . text cleancode,codesize,controversial,design,naming,unusedcode`
+3. Test with: `phpmd . text cleancode,codesize,controversial,design,naming,unusedcode`
 
 **Resources:**
+
 - [PHPMD Documentation](https://phpmd.org/)
 - [PHPMD Rules](https://phpmd.org/rules/index.html)
 

.github/ISSUE_TEMPLATE/phpstan-failure.md

@@ -13,9 +13,11 @@ assignees: []
 **Date:** {{ date | date('YYYY-MM-DD') }}
 
 ### Description
+
 The PHPStan for WordPress static analysis check has failed during the automated testing process.
 
-### What happened?
+### What Happened
+
 PHPStan for WordPress detected potential code issues during static analysis. This could indicate:
 
 - Type safety issues specific to WordPress APIs
@@ -24,16 +26,18 @@ PHPStan for WordPress detected potential code issues during static analysis. Thi
 - Incorrect usage of WordPress functions or hooks
 
 ### Next Steps
-1. Review the workflow logs at the link above
-2. Check the specific PHPStan error messages
-3. Fix any identified code issues
-4. Ensure WordPress-specific type annotations are correct
-5. Re-run the workflow to verify fixes
+
+1. Review the workflow logs at the link above.
+2. Check the specific PHPStan error messages.
+3. Fix any identified code issues.
+4. Ensure WordPress-specific type annotations are correct.
+5. Re-run the workflow to verify fixes.
 
 ### Additional Information
-- This check uses WordPress-specific PHPStan rules
-- The analysis helps catch WordPress-related coding issues early
-- Consider updating code to follow WordPress best practices
+
+- This check uses WordPress-specific PHPStan rules.
+- The analysis helps catch WordPress-related coding issues early.
+- Consider updating code to follow WordPress best practices.
 
 ---
 *This issue was automatically created by the PHPStan for WordPress workflow failure.*

.github/ISSUE_TEMPLATE/plugin-check-failure.md

@@ -17,44 +17,44 @@ The WordPress Plugin Check action has identified issues with the Optimizations A
 
 ### Next Steps
 
-This issue has been automatically created because the WordPress Plugin Check found issues with the plugin that should be addressed. The check performed the following specific tests:
+This issue was automatically created because WordPress Plugin Check found issues with the plugin. The check performed these tests:
+
+#### Categories
 
-#### Categories:
 - **Accessibility**: Checks for accessibility compliance issues
 - **General**: General WordPress coding standards and best practices
 - **Performance**: Tests that identify performance bottlenecks
-- **Plugin Repo**: Requirements for WordPress.org plugin repository
+- **Plugin Repo**: Requirements for the WordPress.org plugin repository
 - **Security**: Security-focused checks to identify vulnerabilities
 
-#### Specific Checks:
+#### Specific Checks
+
 - **i18n_usage**: Proper internationalization usage
-- **code_obfuscation**: Detecting potentially obfuscated code
-- **direct_db_queries**: Identifying direct database queries that bypass WordPress APIs
-- **enqueued_scripts_in_footer**: Ensuring scripts are properly enqueued in the footer
-- **enqueued_scripts_size**: Checking for excessively large script files
-- **enqueued_styles_scope**: Ensuring styles are properly scoped
-- **file_type**: Checking for proper file types and formats
-- **late_escaping**: Ensuring output is properly escaped
-- **localhost**: Checking for references to localhost or development environments
-- **no_unfiltered_uploads**: Ensuring uploads are properly filtered
-- **performant_wp_query_params**: Checking for inefficient WP_Query parameters
-- **plugin_header_text_domain**: Verifying correct text domain in plugin header
-- **plugin_readme**: Checking the plugin readme file format
+- **code_obfuscation**: Potentially obfuscated code
+- **direct_db_queries**: Direct database queries that bypass WordPress APIs
+- **enqueued_scripts_in_footer**: Scripts that should be enqueued in the footer
+- **enqueued_scripts_size**: Excessively large script files
+- **enqueued_styles_scope**: Styles that need stronger scoping
+- **file_type**: Proper file types and formats
+- **late_escaping**: Output that should be escaped later
+- **localhost**: References to localhost or development environments
+- **no_unfiltered_uploads**: Uploads that should be filtered
+- **performant_wp_query_params**: Inefficient `WP_Query` parameters
+- **plugin_header_text_domain**: Correct text domain in the plugin header
+- **plugin_readme**: Plugin readme file format
 - **plugin_review_phpcs**: PHP CodeSniffer checks for WordPress standards
-- **plugin_updater**: Checking plugin update mechanisms
-- **trademarks**: Checking for potential trademark violations
+- **plugin_updater**: Plugin update mechanisms
+- **trademarks**: Potential trademark violations
 
-#### Recommended Actions:
+#### Recommended Actions
 
-1. Review the workflow logs for specific error messages and warnings
-2. Address each identified issue in the plugin code
-3. Test locally using the [WordPress Plugin Check tool](https://github.com/WordPress/plugin-check) to verify fixes
-4. Submit a pull request with the necessary changes
+1. Review the workflow logs for specific error messages and warnings.
+2. Address each identified issue in the plugin code.
+3. Test using the [WordPress Plugin Check tool](https://github.com/WordPress/plugin-check) to verify fixes.
+4. Submit a pull request with the necessary changes.
 
 Once all issues are fixed, please close this issue and reference it in the changelog.
 
 ### About WordPress Plugin Check
 
 The WordPress Plugin Check tool helps plugin authors create plugins that follow WordPress best practices. It checks for issues related to security, performance, and compatibility to ensure plugins work well in the WordPress ecosystem.
-
----

.github/ISSUE_TEMPLATE/psalm-failure.md

@@ -11,24 +11,28 @@ assignees: []
 The Psalm static analysis check has failed for the repository.
 
 **Failure Details:**
+
 - **PHP Version:** {{ env.PHP_VERSION }}
 - **Workflow Run:** [View Details]({{ env.WORKFLOW_URL }})
 - **Run ID:** {{ env.RUN_ID }}
 
 **What happened:**
+
 Psalm has detected potential issues in the code through static analysis.
 
 **What needs to be done:**
-1. Review the Psalm output in the failed workflow run
+
+1. Review the Psalm output in the failed workflow run.
 2. Address static analysis issues such as:
    - Type errors
    - Undefined variables or methods
    - Incorrect return types
    - Unused code
    - Potential null pointer issues
-3. Test locally with: `./vendor/bin/psalm`
+3. Test with: `./vendor/bin/psalm`
 
 **Resources:**
+
 - [Psalm Documentation](https://psalm.dev/)
 - [Psalm Error Levels](https://psalm.dev/docs/running_psalm/error_levels/)
 

.github/ISSUE_TEMPLATE/security-failure.md

@@ -11,26 +11,30 @@ assignees: []
 A security vulnerability has been detected in the project dependencies.
 
 **Failure Details:**
+
 - **PHP Version:** {{ env.PHP_VERSION }}
 - **Workflow Run:** [View Details]({{ env.WORKFLOW_URL }})
 - **Run ID:** {{ env.RUN_ID }}
 
 **What happened:**
-The security checker has identified known vulnerabilities in one or more of the project's dependencies.
+
+The security checker identified known vulnerabilities in one or more project dependencies.
 
 **What needs to be done:**
-1. Review the security check output in the failed workflow run
-2. Identify which dependencies have vulnerabilities
-3. Update vulnerable dependencies to secure versions
+
+1. Review the security check output in the failed workflow run.
+2. Identify which dependencies have vulnerabilities.
+3. Update vulnerable dependencies to secure versions.
 4. If updates are not available, consider:
    - Finding alternative packages
    - Applying patches if available
    - Implementing workarounds
-5. Test the application after updates
+5. Test the application after updates.
 
-**⚠️ Priority:** This is a security issue and should be addressed immediately.
+**Priority:** This is a security issue and should be addressed immediately.
 
 **Resources:**
+
 - [Symfony Security Checker](https://github.com/FriendsOfPHP/security-advisories)
 - [WordPress Security Best Practices](https://developer.wordpress.org/plugins/security/)