Hey @olsavmic, what do you mean when you say "without any properties", can you provide a tiny example?

Sure, when you try to serialize class without any properties:

class Foo {}

PropertyNormalizer won't be called (due to the check in PropertyNormalizer::supports) which means that the serializer would fail to construct the object.

If we remove this additional check from PropertyNormalizer, it can construct the object perfectly fine, including call to the constructor.

Replacing PropertyNormalizer by \Symfony\Component\Serializer\Normalizer\ObjectNormalizerwould solve this issue but we do not want to work with all the magic introduced byPropertyAccessor`, PropertyNormalizer perfectly fits our needs except for this edge case.

I simply think that the following check from \Symfony\Component\Serializer\Normalizer\PropertyNormalizer::supports is not needed or can be made optional:

    /**
     * Checks if the given class has any non-static property.
     */
    private function supports(string $class): bool
    {
        $class = new \ReflectionClass($class);

        // We look for at least one non-static property
        do {
            foreach ($class->getProperties() as $property) {
                if (!$property->isStatic()) {
                    return true;
                }
            }
        } while ($class = $class->getParentClass());

        return false;
    }

Indeed, I don't see any reason to enforce having at least one "non-static" property.
The same goes for the GetSetNormalizer

IMHO, as you said, we might add a context value like SUPPORT_EMPTY_OBJECT (name can be challenged) in the PropertyNormalizer and in the GetSetNormalizer (that'll default to false) to allow skipping the extra-check in the supports method

Up for a PR? 😉

Hey, thanks for your report!
There has not been a lot of activity here for a while. Is this bug still relevant? Have you managed to find a workaround?

Hello? This issue is about to be closed if nobody replies.

Waiting for linked PR to be merged #46417

Hey, thanks for your report!
There has not been a lot of activity here for a while. Is this bug still relevant? Have you managed to find a workaround?

@nicolas-grekas @dunglas ping

The release of Symfony 7 is getting pretty close and the implementation of a fix for this issue has been approved as optional feature for v6 and default in v7 (#46417 (comment)).

Would you consider reviewing and releasing this change?
I'm open to any changes, we can keep the default value to FALSE in order to not change the behavior.

To overcome this limitation in the meantime, we're using a custom normalizer for empty objects, which introduces unnecessary logic and is not fully compatible with all the stuff that AbstractObjectNormalizer (which is implemented by PropertyNormalizer, GetSetMethodNormalizer and the more complex ObjectNormalizer) provides.