feat: Enhance post type fields retrieval with fallback cache #72
Conversation
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
- Updated `getPostTypeFields` method in `WpLoupeFieldManager` to gracefully handle REST fetch errors and fallback to a localized cache. - Added error handling and basic validation for the response. chore: Bump version to 0.5.5 - Updated version number in `package.json`, `readme.txt`, and main plugin file. docs: Revise readme for clarity and conciseness - Changed title and description for better clarity. - Updated changelog with new features and fixes for version 0.5.5. test: Add unit tests for schema manager and REST endpoints - Created tests for `SchemaManager`, `REST PostTypeFields`, and `REST Search` to ensure functionality and correctness. - Added tests for settings and token service behaviors. feat: Implement auto-update functionality - Added `WP_Loupe_Auto_Update` class to manage plugin auto-updates with user settings. - Introduced settings toggle for enabling/disabling automatic updates. feat: Migrate schema and ensure post_date field - Created `WP_Loupe_Migration` class to handle schema migrations and ensure `post_date` field exists for all post types. - Implemented logic for reindexing based on site size. feat: Introduce token service for MCP operations - Added `WP_Loupe_Token_Service` class to manage MCP tokens and rate limits. - Implemented methods for creating, revoking, and saving rate limits for tokens. test: Enhance tests for token service and settings - Added tests for rate limits and token revocation to ensure proper functionality.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request introduces several important enhancements and fixes to the WP Loupe plugin, focusing on schema migration, plugin auto-update management, improved test coverage, and REST API robustness. The most notable changes include a migration routine to ensure the presence of the
post_datefield in all indexes, a new settings-driven auto-update toggle, and expanded tests and documentation. Additionally, the REST API handler is now more robust and testable.Schema Migration & Indexing Improvements
WP_Loupe_Migrationclass to ensure thepost_datefield exists for all post types, automatically migrating older installations and triggering a reindex (inline for ≤2000 posts, scheduled otherwise). Admins can opt out viaWP_LOUPE_DISABLE_AUTO_REINDEX.WP_Loupe_Indexerto include a migration helper (ensure_required_columns) that checks and adds thepost_datecolumn and index to the SQLite documents table if missing, preventing fatal errors on upgrade. [1] [2]Plugin Auto-Update Management
WP_Loupe_Auto_Updateclass to enable or disable automatic plugin updates via a settings toggle (defaults to enabled). This respects a constant-based opt-out (WP_LOUPE_DISABLE_AUTO_UPDATE) and user preferences.REST API Enhancements
Testing & Documentation
CHANGELOG.mdwith detailed notes on new features, migration strategies, fixes, and internal refactors.These changes collectively improve the plugin's upgrade safety, maintainability, and extensibility, while providing clearer documentation and better test coverage.