Asmir Mustafic

Currently this feature do not exists yet. PR are welcome :)

hi, thanks for reporting the issue. can you please create a PR with the suggestion in https://github.com/schmittjoh/JMSSerializerBundle/issues/734#issuecomment-791621841 (if it works for you)

see comments on #90

It looks the object is null but the serializer thinks is not.... can you share something more here?

Tests are failing...

yes, you should also check if the directory hes been created

Cool. :) any chance to add a test?

sorry for the late feedback, generally yes, can you reproduce a failing test case?

I personally think that both ```json { "pre74property": null, "initialized74property": "present", "uninitialized74property": null } ``` and ```json { "initialized74property": "present" } ``` are wrong. if `public ?string $uninitialized74property;` was supposed...

The only "acceptable" thing that the serializer could do here is to skip always the serialization of uninitialized props (as suggested by @Tobion), but that would force us to use...