Repository navigation
Support Open Graph images in the next host API - #5
Merged
Merged
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
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.
Add
SsrClient::ogImage(EmbedRequest)for host-owned Open Graph endpoints. It posts the placement's normalized render payload and tokens to sidecarPOST /v1/og, validates the returned image and falls back when no card is available or the request fails.The optional endpoint reaches the product module and participates in the render cache key. Body/header construction is shared with ordinary rendering, retaining existing render limits, response validation and error classification.
Validation: 64 tests / 229 assertions, full-source PHPStan at max level, Composer validation and changed-file PHP syntax checks pass. Tests cover binary results, failures/fallbacks, request limits and tokens, endpoint cache identity, and source/module separation. Includes documentation and the next API's changelog entry.