disallow extra field when denormalization

[IndraGunawan]

i think it would be great if api-platform has built in validation to allow/disallow extra fields when user POST / PUT data

so if user submit data that the property does not exist or the property does not include in denormalization context group, it will be throw validation error like Symfony form type http://symfony.com/doc/current/reference/forms/types/form.html#allow-extra-fields

[backbone87]

The symfony serializer has an Option to check extra props. though not for missing Attributes, which makes the current PUT more like a PATCH

[IndraGunawan]

you're right, but allow_extra_attributes context key was introduced in Symfony 3.3. https://symfony.com/doc/current/components/serializer.html#deserializing-an-object and current api-platform not support extra resource attribute key

[backbone87]

i also needed required attributes. i solved the problem by using a flag within my model that is initialied to false per default and then set to true, if the setter is called. you can then use a Callback validator and a custom method to produce validation errors, if the setter is not called.

its not a beauty but it works.

[dkarlovi]

This is more a feature request than a question, basically

Support allow_extra_attributes=false in API Platform

Is it not?

[meyerbaptiste]

allow_extra_attributes is supported, I just did the test.

[dkarlovi]

@meyerbaptiste Great, can you paste a short sample?

[dkarlovi]

allow_extra_attributes does indeed work, although the error message could use some work (I guess that should be fixed in Symfony).

But, how to enable it? I just it from a SerializerContextBuilderInterface, but it would be cool to be able to enable it from app-wide config and override in resource metadata.

[dunglas]

I agree. Having a global config flag to populate à base normalization and denormalization context would be a nice DX improvement.

Would you mind opening a PR?

[dkarlovi]

Would you mind opening a PR?

I knew somebody would say that. :) But yes, I'll do it. 👍

@dunglas quickly looking at this, most proper way would be ContextTrait? How would you inject the value, adding a setter in the trait? Or rename to ConfigurationAwareContextTrait where we're able to inject a config hash?

[soyuka]

I agree. Having a global config flag to populate à base normalization and denormalization context would be a nice DX improvement.

Coming soon with symfony default context configuration (I hope) + duplicate of #1526

[lucascourot]

For those who wonder how to disable extra fields

/**
 * @ApiResource(
 *     denormalizationContext={"allow_extra_attributes"=false}
 * )
 */