JMSSerializerBug.php

<?php

class Thing
{
    /**
     * @JMS\Type("integer")
     */
    private $fooBar;

    public function getFooBar()
    {
        return $this->fooBar;
    }
}

$json = '{"fooBar": 123}';
$deserializedThing = $serializer->deserialize($json, 'Thing', 'json');

assert(123, $deserializedThing->getFooBar()); 
// FAILS, we get null instead
// Adding @JMS\SerializedName("fooBar") resolves the issue
// Internally, the serializer converts fooBar to foo_bar unless instructed otherwise

This behavior is documented under @SerializedName http://jmsyst.com/libs/serializer/master/reference/annotations

However, this is so counterintuitive, that I think it is a bug. In the example above, there's absolutely no reason why the serializer should interfere with my naming, since both the json and the php code use camelcase.

Moved to schmittjoh/serializer#33