Skip to content

IBX-11553: Made http-cache response taggers more specialized#78

Open
konradoboza wants to merge 8 commits intomainfrom
ibx-11553-reponse-taggers-increased-verbosity
Open

IBX-11553: Made http-cache response taggers more specialized#78
konradoboza wants to merge 8 commits intomainfrom
ibx-11553-reponse-taggers-increased-verbosity

Conversation

@konradoboza
Copy link
Copy Markdown
Contributor

@konradoboza konradoboza commented Apr 1, 2026

🎫 Issue IBX-11553

Regressions: ibexa/commerce#1760

Description:

This serves as a DX improvement in regards to the report from community, it's nicely summarized by @mnocon here: ibexa/documentation-developer#3109.

Generally speaking DispatcherTagger isn't much of a strategy - each tagger that is available here is getting the value regardless if it can work or not with no indication what happened whatsoever.

Several changes within this PR aim to improve the overall situation with keeping BC promise for the custom implementations of Ibexa\Contracts\HttpCache\ResponseTagger\ResponseTagger:

  • I adjusted all existing response taggers to extend AbstractValueTagger - I introduced abstract public function supports(mixed $value): bool; there not to break BC in the interface itself,
  • instead of passing all the values to all the taggers I now implement and trigger supports() method beforehand,
  • custom response taggers don't require supports() method - they will be called as before (added proper deprecartion),
  • I added DisptacherTagger::__toString method to list available implementation tagged with ibexa.cache.http.response.tagger,
  • I removed spec tests for response taggers and replaced them with regular unit tests, providing some more coverage for cases explained above,
  • got rid of several PHPStan issues as a result of the above.

For QA:

Documentation:

@konradoboza konradoboza self-assigned this Apr 1, 2026
@konradoboza konradoboza force-pushed the ibx-11553-reponse-taggers-increased-verbosity branch 3 times, most recently from 67c22f3 to 2df0e85 Compare April 1, 2026 10:52
@konradoboza konradoboza changed the base branch from 4.6 to main April 1, 2026 10:52
@konradoboza konradoboza force-pushed the ibx-11553-reponse-taggers-increased-verbosity branch 8 times, most recently from 0f41e1a to 6512235 Compare April 1, 2026 14:27
@konradoboza konradoboza force-pushed the ibx-11553-reponse-taggers-increased-verbosity branch from 6512235 to 31c7b18 Compare April 1, 2026 14:35
@konradoboza konradoboza changed the title IBX-11553: Made response taggers more verbose instead of silently fai… IBX-11553: Made http-cache response taggers more specialized Apr 1, 2026
@konradoboza konradoboza requested a review from a team April 2, 2026 10:39
@ibexa-workflow-automation-1 ibexa-workflow-automation-1 bot requested review from Steveb-p and mikadamczyk and removed request for a team April 2, 2026 10:39
@konradoboza konradoboza requested a review from barw4 April 7, 2026 10:58
@konradoboza konradoboza closed this Apr 7, 2026
@konradoboza konradoboza reopened this Apr 7, 2026
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Apr 8, 2026

@konradoboza konradoboza requested review from Steveb-p and vidarl April 8, 2026 10:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants