Skip to content

Releases: spryker-community/search-debug

v1.4.1

Choose a tag to compare

@andrebarthelmeshellmuth andrebarthelmeshellmuth released this 28 Aug 15:12
4455392

Patch release. No runtime `require` or behaviour change.

Added

  • checkGlueApiWiring() in SearchDebugCheckInstallationConsole — a WARNING (never a failure; a shop that runs no Glue Storefront app is a valid config) that names the exact remedy for the two silent ways GET /catalog-search ends up without searchDebug: the additive schema merge never generated, or the project-level CatalogSearchStorefrontProvider override missing / not referencing the searchDebug key. 4 tests + GlueApiResourceFixture. (#43)

Documented

  • extra.dependency-pins note on symfony/security-guard: 5.4.0-BETA1 — it is a resolution pin (no src/ usage) holding symfony/security-core on a PHP-8.3-compatible line via spryker/api-platform; a phantom-dependency audit flags it and it must not be dropped. (#43)
  • OpenSearch 3.5 / Lucene 10.3 compatibility verified end-to-end; new docs/opensearch-3.x-migration.md. (#42)

v1.4.0

Choose a tag to compare

@andrebarthelmeshellmuth andrebarthelmeshellmuth released this 28 Aug 15:12
fca1803

Added

  • Glue API support via API Platform: additive searchDebug property on core's catalog-search resource (GET /catalog-search), the same permission-gated payload the SRP overlay already exposes to Yves. Schema-only merge — actually surfacing the value requires a small project-level Provider override; see the README's new "Glue REST API" section for the required wiring and a symlinked-install (composer path-repo) Finder gotcha. (#40)

Fixed

  • Corrected composer dependency declarations found by a full requires-vs-usage audit. (#41)
  • Unblocked composer resolution for spryker/api-platform: pinned symfony/security-guard to the one pre-release that actually supports Symfony 6.4/7 security-core (its stable siblings cap at Symfony 5) — same root cause and fix as spryker-community/search-feedback v1.5.0.
  • Applied Rector's IfToNullCoalescingAssignRector (dev-tooling drift from an unpinned rector/rector floor, unrelated to the above).

v1.3.4

Choose a tag to compare

@andrebarthelmeshellmuth andrebarthelmeshellmuth released this 28 Aug 15:12
8c04deb

CI-only patch release.

  • Bumped actions/checkout from v4 to v7 in the GitHub Actions workflows.

v1.3.3

Choose a tag to compare

@andrebarthelmeshellmuth andrebarthelmeshellmuth released this 28 Aug 15:12
1e6e9d9

Test-coverage patch release.

  • Added a Zed test suite covering SearchDebugCheckInstallationConsole.

v1.3.2

Choose a tag to compare

@andrebarthelmeshellmuth andrebarthelmeshellmuth released this 28 Aug 15:12
62ec43f

Docs/CI-only patch release.

  • Restored README screenshots against search-feedback's fictional "Feldwerk" demo catalog (bundled copy).
  • Fixed a rector finding.
  • Added a fixtures-sync CI job that diffs the bundled demo-catalog CSVs against search-feedback's canonical copy on every push/PR, so a future edit to one without the other fails CI instead of drifting silently.

v1.3.1

Choose a tag to compare

@andrebarthelmeshellmuth andrebarthelmeshellmuth released this 28 Aug 15:12
bd92840

Patch release, docs/CI only — no runtime or public-API changes.

  • State plainly in the README that spryker-community/* is an independent, community-built namespace with no official Spryker affiliation (#33)
  • Fix stale spryker-search-debugger repo references (CHANGELOG, SECURITY, composer.json) now that the repo is spryker-search-debug (#33)
  • Update the Packagist-namespace note to reflect that we're now in contact with Spryker's community program about publishing this package there properly (#34)
  • CI: add an xmllint job to catch malformed phpcs/phpmd ruleset XML; pin dev tooling versions to stop CI drift

v1.3.0

Choose a tag to compare

@andrebarthelmeshellmuth andrebarthelmeshellmuth released this 28 Aug 15:12
a7aa5ee

Minor release: adds a word-level analysis page (per-field source breakdown, tokenization word badges resolved from the real analyzer's own boundaries) and a SKU-lookup widget, both with Presentation-suite coverage. Also stops committing Spryker's own generated PageIndexMap.php fixture -- it's now regenerated standalone in CI (see tests/_ci-standalone/generate-index-map.php), the same convention transfers already use.

What's Changed

Full Changelog: andrebarthelmeshellmuth/spryker-search-debug@v1.2.3...v1.3.0

v1.2.3

Choose a tag to compare

@andrebarthelmeshellmuth andrebarthelmeshellmuth released this 28 Aug 15:12
6560339

Patch release: phpstan (level 8) is now gated in CI via a standalone composer phpstan-ci variant, alongside the existing Portable Codeception test job — both now block merges to main as required status checks, not just phpcs/rector/floors. No missing dependencies found here — this package's composer.json was already complete.

What's Changed

Full Changelog: andrebarthelmeshellmuth/spryker-search-debug@v1.2.2...v1.2.3

v1.2.2

Choose a tag to compare

@andrebarthelmeshellmuth andrebarthelmeshellmuth released this 28 Aug 15:12
81f8fd1

Patch release: the package's Codeception test suite can now run standalone in CI, without a full Spryker application context. A dedicated tests/_ci-standalone bootstrap generates just the transfer classes this package's tests need, so contributors and CI get fast, isolated feedback on pull requests. No source changes.

What's Changed

Full Changelog: andrebarthelmeshellmuth/spryker-search-debug@v1.2.1...v1.2.2

v1.2.1

Choose a tag to compare

@andrebarthelmeshellmuth andrebarthelmeshellmuth released this 28 Aug 15:12
eca12f3

A maintenance release from a full release-testing pass (Rector, phpcs/phpmd, phpstan level 8, dependency floors, the complete test suite, a coverage-gap scan, docs refresh and a code review). No runtime behaviour changes — the fixes are in test infrastructure, packaging and documentation.

Fixed

  • Test autoloading under a host shop. Two Client-suite test files fatal-errored (Trait/Class not found) whenever they ran through a consuming shop's own Composer autoloader — the normal way these tests actually run — because their fixture classes lived only in autoload-dev, which a consumer never installs. The two fixture sub-namespaces are now exposed via regular autoload, the same pattern spryker/testify uses for its own test helpers.
  • Two Presentation tests that could never pass hard-asserted fulltext_synonyms content, but the demo shop's page.json configures no synonym filter at all. Both are now fail-soft (skip with a comment), matching the convention this suite already uses for legitimately environment-dependent traces.
  • 5 phpcs docblock mismatches in CheckInstallationControllerTest's inline fake container.
  • README: documented the required search-debug-product-wrapper div in installation step 6 (a real gap found by a fresh install walkthrough), and corrected the stale test count.

Coverage

Two remaining 0%-coverage classes closed, both now at 100%: ComponentConfigController (permission gate, parameter validation, not-found handling) and SearchDebugTwigPlugin (token-colour assignment, including wraparound and duplicate-token collapsing).

Current suite: 303 tests — 154 Client, 126 Yves, 23 Presentation/WebDriver — all green, with phpcs, phpmd, Rector, composer validate --strict and dependency-floor checks clean on PHP 8.3 and 8.4.

What's Changed

Full Changelog: andrebarthelmeshellmuth/spryker-search-debug@v1.2.0...v1.2.1