Skip to content
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 Direct_DB_Queries_Check #336

Merged
merged 2 commits into from
Jan 3, 2024

Conversation

ernilambar
Copy link
Member

Fixes #29

Note:

  • I have added tests to cover my change.
  • All new and existing tests pass.

@ernilambar
Copy link
Member Author

Copy link
Member

@felixarntz felixarntz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ernilambar I think this looks good. Since that is clearly a WordPress best practice, and since it's a simple check that only triggers warnings, I think it could be merged as is.

Copy link
Member

@mukeshpanchal27 mukeshpanchal27 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @ernilambar for the PR. I've provided some feedback, but aside from those points, everything appears to be in good shape from my perspective.

@ernilambar
Copy link
Member Author

ernilambar commented Jan 3, 2024

PR has been updated and ready to review.

@mukeshpanchal27 mukeshpanchal27 merged commit 0162771 into WordPress:trunk Jan 3, 2024
25 checks passed
@ernilambar ernilambar deleted the direct-db-queries-check branch January 3, 2024 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create Direct_DB_Queries_Check
3 participants