Using a DTO throws a 500 validation exception
up vote
0
down vote
favorite
Following the documentation How to Use a DTO for Writing, I'm getting a 500 validation error:
{
"@context": "/api/contexts/Error",
"@type": "hydra:Error",
"hydra:title": "An error occurred",
"hydra:description": "Cannot validate values of type "NULL" automatically. Please provide a constraint.",
...
The DTO is the same as documented (note the specific namespace):
namespace AcmeInfrastructureDto;
use ApiPlatformCoreAnnotationApiResource;
use SymfonyComponentValidatorConstraints as Assert;
/**
* @ApiResource(
* collectionOperations={
* "post"={
* "path"="/do-something",
* },
* },
* itemOperations={},
* )
*/
final class DoSomethingRequest
{
/**
* @AssertNotBlank
* @AssertEmail
*/
public $email;
}
Here's the configuration:
# api_platform.yaml
api_platform:
mapping:
paths:
- '%kernel.project_dir%/src/Infrastructure/Dto'
php symfony api-platform.com
asked Nov 16 at 10:02
David
83321021
add a comment |
up vote
0
down vote
favorite
Following the documentation How to Use a DTO for Writing, I'm getting a 500 validation error:
{
"@context": "/api/contexts/Error",
"@type": "hydra:Error",
"hydra:title": "An error occurred",
"hydra:description": "Cannot validate values of type "NULL" automatically. Please provide a constraint.",
...
The DTO is the same as documented (note the specific namespace):
namespace AcmeInfrastructureDto;
use ApiPlatformCoreAnnotationApiResource;
use SymfonyComponentValidatorConstraints as Assert;
/**
* @ApiResource(
* collectionOperations={
* "post"={
* "path"="/do-something",
* },
* },
* itemOperations={},
* )
*/
final class DoSomethingRequest
{
/**
* @AssertNotBlank
* @AssertEmail
*/
public $email;
}
Here's the configuration:
# api_platform.yaml
api_platform:
mapping:
paths:
- '%kernel.project_dir%/src/Infrastructure/Dto'
php symfony api-platform.com
asked Nov 16 at 10:02
David
83321021
Is your top level namespace reallyAcme?
– Andrei
Nov 16 at 10:12
Yes, the namespace has been changed from the default one to the name of the organization.
– David
Nov 16 at 10:15
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Following the documentation How to Use a DTO for Writing, I'm getting a 500 validation error:
{
"@context": "/api/contexts/Error",
"@type": "hydra:Error",
"hydra:title": "An error occurred",
"hydra:description": "Cannot validate values of type "NULL" automatically. Please provide a constraint.",
...
The DTO is the same as documented (note the specific namespace):
namespace AcmeInfrastructureDto;
use ApiPlatformCoreAnnotationApiResource;
use SymfonyComponentValidatorConstraints as Assert;
/**
* @ApiResource(
* collectionOperations={
* "post"={
* "path"="/do-something",
* },
* },
* itemOperations={},
* )
*/
final class DoSomethingRequest
{
/**
* @AssertNotBlank
* @AssertEmail
*/
public $email;
}
Here's the configuration:
# api_platform.yaml
api_platform:
mapping:
paths:
- '%kernel.project_dir%/src/Infrastructure/Dto'
php symfony api-platform.com
asked Nov 16 at 10:02
David
83321021
Following the documentation How to Use a DTO for Writing, I'm getting a 500 validation error:
{
"@context": "/api/contexts/Error",
"@type": "hydra:Error",
"hydra:title": "An error occurred",
"hydra:description": "Cannot validate values of type "NULL" automatically. Please provide a constraint.",
...
The DTO is the same as documented (note the specific namespace):
namespace AcmeInfrastructureDto;
use ApiPlatformCoreAnnotationApiResource;
use SymfonyComponentValidatorConstraints as Assert;
/**
* @ApiResource(
* collectionOperations={
* "post"={
* "path"="/do-something",
* },
* },
* itemOperations={},
* )
*/
final class DoSomethingRequest
{
/**
* @AssertNotBlank
* @AssertEmail
*/
public $email;
}
Here's the configuration:
# api_platform.yaml
api_platform:
mapping:
paths:
- '%kernel.project_dir%/src/Infrastructure/Dto'
php symfony api-platform.com
php symfony api-platform.com
asked Nov 16 at 10:02
David
83321021
asked Nov 16 at 10:02
David
83321021
edited Nov 16 at 14:23
asked Nov 16 at 10:02
David
83321021
asked Nov 16 at 10:02
David
83321021
asked Nov 16 at 10:02
David
83321021
83321021
Is your top level namespace reallyAcme?
– Andrei
Nov 16 at 10:12
Yes, the namespace has been changed from the default one to the name of the organization.
– David
Nov 16 at 10:15
add a comment |
Is your top level namespace reallyAcme?
– Andrei
Nov 16 at 10:12
Yes, the namespace has been changed from the default one to the name of the organization.
– David
Nov 16 at 10:15
Is your top level namespace really
Acme?– Andrei
Nov 16 at 10:12
Is your top level namespace really
Acme?– Andrei
Nov 16 at 10:12
Yes, the namespace has been changed from the default one to the name of the organization.
– David
Nov 16 at 10:15
Yes, the namespace has been changed from the default one to the name of the organization.
– David
Nov 16 at 10:15
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Actually, I was calling the endpoint sending FormData encoded payload. It turns out that "API Platform only supports raw documents as request input" (cf. https://api-platform.com/docs/core/form-data/).
Nevertheless, I believe that would be nice to throw a more explicit exception in this case than letting the RecursiveContextualValidator of Symfony handle the case with an obscure message.
answered Nov 19 at 10:43
David
83321021
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Actually, I was calling the endpoint sending FormData encoded payload. It turns out that "API Platform only supports raw documents as request input" (cf. https://api-platform.com/docs/core/form-data/).
Nevertheless, I believe that would be nice to throw a more explicit exception in this case than letting the RecursiveContextualValidator of Symfony handle the case with an obscure message.
answered Nov 19 at 10:43
David
83321021
add a comment |
up vote
0
down vote
accepted
Actually, I was calling the endpoint sending FormData encoded payload. It turns out that "API Platform only supports raw documents as request input" (cf. https://api-platform.com/docs/core/form-data/).
Nevertheless, I believe that would be nice to throw a more explicit exception in this case than letting the RecursiveContextualValidator of Symfony handle the case with an obscure message.
answered Nov 19 at 10:43
David
83321021
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Actually, I was calling the endpoint sending FormData encoded payload. It turns out that "API Platform only supports raw documents as request input" (cf. https://api-platform.com/docs/core/form-data/).
Nevertheless, I believe that would be nice to throw a more explicit exception in this case than letting the RecursiveContextualValidator of Symfony handle the case with an obscure message.
answered Nov 19 at 10:43
David
83321021
Actually, I was calling the endpoint sending FormData encoded payload. It turns out that "API Platform only supports raw documents as request input" (cf. https://api-platform.com/docs/core/form-data/).
Nevertheless, I believe that would be nice to throw a more explicit exception in this case than letting the RecursiveContextualValidator of Symfony handle the case with an obscure message.
answered Nov 19 at 10:43
David
83321021
answered Nov 19 at 10:43
David
83321021
answered Nov 19 at 10:43
David
83321021
answered Nov 19 at 10:43
David
83321021
83321021
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53335472%2fusing-a-dto-throws-a-500-validation-exception%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Is your top level namespace really
Acme?– Andrei
Nov 16 at 10:12
Yes, the namespace has been changed from the default one to the name of the organization.
– David
Nov 16 at 10:15