Mysterious behaviour with PUT route

Maybe it’s a (undocumented) new feature, but I have a mysterious behaviour since a while in a project where using nnrestapi.

I have an entrypoint method with this annotations:

/**
* Add debaters to competition
*
* @Api\Route("PUT competition/{competition}/debaters")
* @Api\Access("config[competitionApi]")
* @Api\Example("{'debaters':[1,2,3,4]}")
*
* @param Competition $competition
* @return Response
*/
public function addDebaters(Competition $competition): Response
{
    try {
        $dabaterUids = array_map('intval', $this->request->getBody()['debaters']);
        $currentDebaters = $competition->getDebaters();

This method should add new debaters to a competition later in the code. The debaters to add will be send as a json array like so:

{
    "debaters": [
        860,
        867,
        1100
    ]
}

The Competition model has a propery “debaters” with a getter and setter method.

Since a while, maybe it comes with an update of this extension (nnrestapi), the $competition->getDebaters() call already contains the just send debaters, without I ever had added theme before!

But if I create a breakpoint in line 15 of the example, the database doesn’t contain them.

This is really problematic, because this way, all new added debaters will kick off the previous added ones!

The only workaround I found, was to change {competition} to {competitionUid} (and Competiton to int) and take the competition out of it’s repository by doing $competition = $this->competitionRepository->findByUid($competitionUid).

Is there an other way to fix this problem and when this “feature” comes in?

Comments (8)