Conversation
The function is available since WP 4.7, so we could have been using it since v1.5. It defaults to the same logic but applies an additional filter internally.
Statify will move to 5.1, so there is no reason to stick with WP 4.7 with the upcoming release.
The function is available since WP 4.8 and defaults to the same logic but applies an additional filter internally.
Add PHPStan and WP stubs to our dev-dependencies and configure a CI workflow to run the analysis. We can start at level 3 without any additional code changes required.
Bumps [sonarsource/sonarqube-scan-action](https://github.com/sonarsource/sonarqube-scan-action) from 5 to 6. - [Release notes](https://github.com/sonarsource/sonarqube-scan-action/releases) - [Commits](SonarSource/sonarqube-scan-action@v5...v6) --- updated-dependencies: - dependency-name: sonarsource/sonarqube-scan-action dependency-version: '6' dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
get_sites() is guaranteed to be available on WP 5.1 and later and never returns the legacy array of arrays structure. Drop the redundant checks. We also do not require the fill site object, so let's just fetch IDs.
The function expects the subject parameter to be a string. Prevent warnings and pass an empty string. We are only interested in catching invalid expressions, so the actual subject does not matter and should be as short as possible.
|
🔍 WordPress Plugin Check Report
📊 Report
|
| 📍 Line | 🔖 Check | 💬 Message |
|---|---|---|
167 |
WordPress.DB.DirectDatabaseQuery.DirectQuery | Use of a direct database call is discouraged. |
167 |
WordPress.DB.DirectDatabaseQuery.NoCaching | Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete(). |
177 |
WordPress.DB.DirectDatabaseQuery.DirectQuery | Use of a direct database call is discouraged. |
177 |
WordPress.DB.DirectDatabaseQuery.NoCaching | Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete(). |
189 |
WordPress.DB.DirectDatabaseQuery.DirectQuery | Use of a direct database call is discouraged. |
189 |
WordPress.DB.DirectDatabaseQuery.NoCaching | Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete(). |
🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.