remoteclient
commented
5 years ago With this post I want to bring some clarity to the issue and show some investigation results. 'Therefore I will write two post with similar issues.
First:
I have a Pet Entity which holds an array called $sexTypeChoices and its getter.
/**
* @var array
*/
public static $sexTypeChoices = [
self::SEX_TYPE_FEMALE => 'sex_type.female',
self::SEX_TYPE_MALE => 'sex_type.male'
];
/**
* @return array
*/
public static function getSexTypeChoices(): array
{
return self::$sexTypeChoices;
}This one has an extra endpoint where only this property delivered to the client (with extra serialization group).
<collectionOperation name="sex_type_choices">
<attribute name="method">GET</attribute>
<attribute name="access_control">is_granted('ROLE_MWS_NC_LIST')</attribute>
<attribute name="path">pets/sex_type_choices</attribute>
<attribute name="controller">MWS\NutritionCalculatorBundle\Controller\SexTypeChoices</attribute>
<attribute name="normalization_context">
<attribute name="groups">
<attribute name="group">mws_nc_sex_type_choices_read</attribute>
</attribute>
</attribute>
</collectionOperation>If I call this endpint I get the correct result but the the swagger part which shows the expected result is empty:
[
{}
]Before the update to v2.3.3 swagger showed the correct expected result like:
[
{
"sexTypeChoices": [
"string"
]
}
]This bug was introduced with commit #2788
if (!$propertyMetadata->isReadable() && !$propertyMetadata->isWritable()) {
continue;
}Since I get a correct result by calling the endpoint, the property IS readable. So either the condition is wrong or isReadable returns a wrong result. As this was working before the commit I consider this a BC break.
teohhanhui
As the title suggests, non-mapped properties are not shown in swagger output anymore. There are different scenarios. Sometimes one entity has a non-mapped property, some entities have other non-mapped entities with naturally also non-mapped properties. They all have in commen, that they don't appear in swagger anymore. They also have propper getters and setters. Serialization/Dezerialization of them are working like before.