Merged
Conversation
vincentchalamon
requested changes
Feb 17, 2026
soyuka
added a commit
to soyuka/core
that referenced
this pull request
Mar 17, 2026
…DocumentationNormalizer | Q | A | ------------- | --- | Branch? | 4.2 | Tickets | api-platform/demo#594 | License | MIT | Doc PR | ∅ When hydra_prefix is false (default since 4.x), $hydraPrefix concatenation produces bare terms ("member", "Collection") that JSON-LD expands as relative IRIs instead of Hydra namespace IRIs, breaking api-doc-parser.
vincentchalamon
force-pushed
the
hydra-docs
branch
2 times, most recently
from
54f2879 to
22bfb0b
Compare
vincentchalamon
force-pushed
the
hydra-docs
branch
from
22bfb0b to
ed75132
Compare
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
2 participants
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 PR demonstrates an issue and potential solution when using multiple
#[ApiResource]attributes on a single entity with different URI templates.When a resource class has multiple
#[ApiResource]declarations with different URI templates (e.g.,/admin/multi_route_booksand/multi_route_books), the client generator only generates types for the resource that appears in the JSON-LD entrypoint, typically missing the other routes.Example:
Using 2 different shortName will do the trick, api-platform/core#7746 will fix the behavior (as without the patch this won't work).
We'll also add an automatic way of handling this inside API Platform so this PR may not be needed in the end (for now its just a showcase).
We also need to test that @api-platform/admin is still working.