-
-
Notifications
You must be signed in to change notification settings - Fork 918
Improve Input/Output with normalizers #2495
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.
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
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,212 @@ | ||
| Feature: DTO input and output | ||
| In order to use a hypermedia API | ||
| As a client software developer | ||
| I need to be able to use DTOs on my resources as Input or Output objects. | ||
|
|
||
| @createSchema | ||
| Scenario: Create a resource with a custom Input | ||
| When I add "Content-Type" header equal to "application/ld+json" | ||
| And I send a "POST" request to "/dummy_dto_customs" with body: | ||
| """ | ||
| { | ||
| "foo": "test", | ||
| "bar": 1 | ||
| } | ||
| """ | ||
| Then the response status code should be 201 | ||
| And the response should be in JSON | ||
| And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8" | ||
| And the JSON should be equal to: | ||
| """ | ||
| { | ||
| "@context": "/contexts/DummyDtoCustom", | ||
| "@id": "/dummy_dto_customs/1", | ||
| "@type": "DummyDtoCustom", | ||
| "lorem": "test", | ||
| "ipsum": "1", | ||
| "id": 1 | ||
| } | ||
| """ | ||
|
|
||
| @createSchema | ||
| Scenario: Get an item with a custom output | ||
| Given there is a DummyCustomDto | ||
| When I send a "GET" request to "/dummy_dto_custom_output/1" | ||
| 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" | ||
| And the JSON should be a superset of: | ||
| """ | ||
| { | ||
| "@context": { | ||
| "@vocab": "http://example.com/docs.jsonld#", | ||
| "hydra": "http://www.w3.org/ns/hydra/core#", | ||
| "foo": { | ||
| "@type": "@id" | ||
| }, | ||
| "bar": { | ||
| "@type": "@id" | ||
| } | ||
| }, | ||
| "@type": "CustomOutputDto", | ||
| "foo": "test", | ||
| "bar": 1 | ||
| } | ||
| """ | ||
|
|
||
| @createSchema | ||
| Scenario: Get a collection with a custom output | ||
| Given there are 2 DummyCustomDto | ||
| When I send a "GET" request to "/dummy_dto_custom_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" | ||
| And the JSON should be a superset of: | ||
| """ | ||
| { | ||
| "@context": "/contexts/DummyDtoCustom", | ||
| "@id": "/dummy_dto_customs", | ||
| "@type": "hydra:Collection", | ||
| "hydra:member": [ | ||
| { | ||
| "foo": "test", | ||
| "bar": 1 | ||
| }, | ||
| { | ||
| "foo": "test", | ||
| "bar": 2 | ||
| } | ||
| ], | ||
| "hydra:totalItems": 2 | ||
| } | ||
| """ | ||
|
|
||
| @createSchema | ||
| Scenario: Create a DummyCustomDto object without output | ||
| When I add "Content-Type" header equal to "application/ld+json" | ||
| And I send a "POST" request to "/dummy_dto_custom_post_without_output" with body: | ||
| """ | ||
| { | ||
| "lorem": "test", | ||
| "ipsum": "1" | ||
| } | ||
| """ | ||
| Then the response status code should be 201 | ||
| And the response should be empty | ||
|
|
||
| @createSchema | ||
| Scenario: Create and update a DummyInputOutput | ||
| When I add "Content-Type" header equal to "application/ld+json" | ||
| And I send a "POST" request to "/dummy_dto_input_outputs" with body: | ||
| """ | ||
| { | ||
| "foo": "test", | ||
| "bar": 1 | ||
| } | ||
| """ | ||
| Then the response status code should be 201 | ||
| And the JSON should be a superset of: | ||
| """ | ||
| { | ||
| "@context": { | ||
| "@vocab": "http://example.com/docs.jsonld#", | ||
| "hydra": "http://www.w3.org/ns/hydra/core#", | ||
| "baz": { | ||
| "@type": "@id" | ||
| }, | ||
| "bat": { | ||
| "@type": "@id" | ||
| } | ||
| }, | ||
| "@type": "OutputDto", | ||
| "baz": 1, | ||
| "bat": "test" | ||
| } | ||
| """ | ||
| When I add "Content-Type" header equal to "application/ld+json" | ||
| And I send a "PUT" request to "/dummy_dto_input_outputs/1" with body: | ||
| """ | ||
| { | ||
| "foo": "test", | ||
| "bar": 2 | ||
| } | ||
| """ | ||
| Then the response status code should be 200 | ||
| And the JSON should be a superset of: | ||
| """ | ||
| { | ||
| "@context": { | ||
| "@vocab": "http:\/\/example.com\/docs.jsonld#", | ||
| "hydra": "http:\/\/www.w3.org\/ns\/hydra\/core#", | ||
| "baz": { | ||
| "@type": "@id" | ||
| }, | ||
| "bat": { | ||
| "@type": "@id" | ||
| } | ||
| }, | ||
| "@type": "OutputDto", | ||
| "baz": 2, | ||
| "bat": "test" | ||
| } | ||
| """ | ||
|
|
||
| @!mongodb | ||
soyuka marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| @createSchema | ||
| Scenario: Use DTO with relations on User | ||
| When I add "Content-Type" header equal to "application/ld+json" | ||
| And I send a "POST" request to "/users" with body: | ||
| """ | ||
| { | ||
| "username": "soyuka", | ||
| "plainPassword": "a real password", | ||
| "email": "soyuka@example.com" | ||
| } | ||
| """ | ||
| Then the response status code should be 201 | ||
| When I add "Content-Type" header equal to "application/ld+json" | ||
| And I send a "PUT" request to "/users/recover/1" with body: | ||
| """ | ||
| { | ||
| "user": "/users/1" | ||
| } | ||
| """ | ||
| Then the response status code should be 200 | ||
| And the JSON should be a superset of: | ||
| """ | ||
| { | ||
| "@context": { | ||
| "@vocab": "http://example.com/docs.jsonld#", | ||
| "hydra": "http://www.w3.org/ns/hydra/core#", | ||
| "dummy": { | ||
| "@type": "@id" | ||
| } | ||
| }, | ||
| "@type": "RecoverPasswordOutput", | ||
| "dummy": "/dummies/1" | ||
| } | ||
| """ | ||
|
|
||
| @!mongodb | ||
| @createSchema | ||
| Scenario: Create a resource that has a non-resource DTO relation. | ||
| When I add "Content-Type" header equal to "application/ld+json" | ||
| And I send a "POST" request to "/non_relation_resources" with body: | ||
| """ | ||
| {"relation": {"foo": "test"}} | ||
| """ | ||
| Then the response status code should be 201 | ||
| And the response should be in JSON | ||
| And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8" | ||
| And the JSON should be equal to: | ||
| """ | ||
| { | ||
| "@context": "/contexts/NonRelationResource", | ||
| "@id": "/non_relation_resources/1", | ||
| "@type": "NonRelationResource", | ||
| "relation": { | ||
| "foo": "test" | ||
| }, | ||
| "id": 1 | ||
| } | ||
| """ | ||
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.