[Serializer] Attribute SerializedName ignored when property name is the same as the related (get|has|can) method

[systemasis]

Symfony version(s) affected

7.0.*

Description

Symfony serializer ignores the attribute SerializedName for properties sharing the same name as the related method shall it start by can, has or get.

How to reproduce

Clone this repository created specifically and use the following command :

bin/console app:test:test

This will output the string of a json serialized App\Entity\ListView object.

Expected output :

"{"free_trial":true,"can_subscribe":false,"has_answers":true,"get_ready":false}"

Current output :

"{"free_trial":true,"subscribe":false,"answers":true,"ready":false}"

Possible Solution

No response

Additional Context

No response

[NeilPeyssard]

Hello,

In a regular use case, you'll probably never call your properties with the same as their accessors (e.g. subscribe instead of canSubscribe).

But after digging around your problem, I can reproduce it. I'll try to work on it, but let's wait for somebody more experienced to see if it's not the expected behavior.

Just for your information, the command is missing in your project, but I guess it looks like this ?

<?php

namespace App\Command;

use App\Entity\ListView;
use Symfony\Component\Console\Attribute\AsCommand;
use Symfony\Component\Console\Command\Command;
use Symfony\Component\Console\Input\InputInterface;
use Symfony\Component\Console\Output\OutputInterface;
use Symfony\Component\Serializer\SerializerInterface;

#[AsCommand(name: 'app:test:test')]
class TestCommand extends Command
{
    public function __construct(
        private readonly SerializerInterface $serializer
    ) {
        parent::__construct();
    }

    protected function execute(InputInterface $input, OutputInterface $output): int
    {
        $listView = new ListView(true, false, true, false);
        $output->writeln($this->serializer->serialize($listView, 'json'));

        return Command::SUCCESS;
    }
}

[systemasis]

I indeed forgot the command and apologize for this but you got it. I'll commit it anyway.

As for the "regular use case", I do agree with you but this would be considering people are perfect beings or at least fluent enough in english to avoid literal translations.
I encountered this problem because I had to serialize an existing object in my project. I managed to workaround it by renaming both the property and the method but this is not always possible.

[NeilPeyssard]

Hello,

I've open a PR to fix your issue. See #54148

[chalasr]

Fix reverted in #54635, should be resubmitted against the development branch.