Skip to content

test(jsonld): type inconsistency when using itemUriTemplate #7650

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
soyuka merged 1 commit into from
Jan 8, 2026
+6 −1
Merged

test(jsonld): type inconsistency when using itemUriTemplate #7650

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@
* [21aa2572d](https://github.com/api-platform/core/commit/21aa2572d8fef2b3f05f7307c51348a6c9767e45) feat(elasticsearch): add SSL options for Elasticsearch configuration (#4059)
* [ba0c76c](https://github.com/api-platform/core/commit/ba0c76c6f5c8afa8622e87a155b8b99f453d6453) feat(doctrine): remove put & path for readonly entity (#7019)

### Breaking changes

* When using `output` with `itemUriTemplate` on a collection operation, the JSON-LD `@type` will now use the resource class name instead of the output DTO class name for semantic consistency with `itemUriTemplate` behavior.

## v4.2.11

### Bug fixes
Expand Down
3 changes: 2 additions & 1 deletion features/jsonld/input_output.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -379,6 +379,7 @@ Feature: JSON-LD DTO input and output
Then the response status code should be 200
And the response should be in JSON
And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
Then print last JSON response
And the JSON should be valid according to this schema:
"""
{
Expand All @@ -400,7 +401,7 @@ Feature: JSON-LD DTO input and output
"required": ["@id", "@type", "foo", "bar"],
"properties": {
"@id": {"pattern": "/dummy_foos/bar"},
"@type": {"pattern": "^DummyCollectionDtoOutput$"},
"@type": {"pattern": "^DummyFooCollectionDto$"},
"foo": {"type": "string"},
"bar": {"type": "integer"}
}
Expand Down
Loading