Repository navigation
Remove the Rust parser extension and its documentation - #566
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
🤖 Lexer benchmarkChanges to lexer-related files were detected and triggered a benchmark:
Note: Hosted runners are noisy, and absolute numbers vary. Treat the results with caution and verify them locally. To reproduce locally: |
## Motivation for the change, related issues [WordPress/sqlite-database-integration#566](WordPress/sqlite-database-integration#566) removes the Rust MySQL parser extension. ## Implementation details Remove the Query API test that downloads the published `wp_mysql_parser` WASM build, along with its unused manifest URL. Keep the `intl` manifest-loading test and the invalid-manifest checks. ## Testing Instructions (or ideally a Blueprint) Run the Query API extension tests in Chromium. All four remaining tests pass locally. Lint, formatting, and test collection also pass. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## Summary by CodeRabbit * **Tests** * Removed an automated end-to-end check for loading the SQLite parser extension from a remote manifest and verifying its reported state and token count. * Automated coverage continues to check the `intl` manifest and manifest error cases. This change affects test coverage only; it does not indicate a change to extension functionality. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Removes the Rust MySQL lexer/parser package, its PHP bridge, native-only tests and benchmarks, CI jobs, WASM publishing, and docs.
The driver and benchmarks now always use PHP. Parser reuse, parser type/AST checks, and the PHP 7.2–8.5/SQLite CI matrix remain.
Testing
Summary by CodeRabbit