Skip to content

Stabilize classic menu cache keys and purge tracking - #241

Merged
mehul0810 merged 1 commit into
release/1.8.0from
fix/106-menu-cache-cardinality
Aug 11, 2026
Merged

Stabilize classic menu cache keys and purge tracking#241
mehul0810 merged 1 commit into
release/1.8.0from
fix/106-menu-cache-cardinality

Conversation

@mehul0810

Copy link
Copy Markdown
Collaborator

Summary

  • replace full query-state menu cache keys with stable output-affecting signatures
  • retain compatibility for query-aware walkers through an explicit filter and bounded custom segments
  • cap tracked variants at 100, evict the oldest entry, recover safely from malformed tracking data, and purge by menu ID
  • document the key contract and add unit plus disposable classic-theme browser coverage

Validation

  • composer lint (91 PHP files)
  • vendor/bin/phpunit (148 tests, 482 assertions)
  • npm run test:js (11 suites, 40 tests)
  • npm run lint
  • npm run build
  • php -d memory_limit=2G vendor/bin/phpstan analyse --no-progress --debug
  • git diff --check

Closes #106

@github-actions

Copy link
Copy Markdown

WordPress Playground Preview

The changes in this pull request can previewed and tested using a WordPress Playground instance.

Open WordPress Playground Preview

@mehul0810
mehul0810 merged commit b0d2eae into release/1.8.0 Aug 11, 2026
12 checks passed
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.

1 participant