Configure a form field like the following:
Afterwards, trying to protect one of the inner fields won't apply the defined PropertyNameDecorator nor combine the composite field name with the inner field's name.
Property name is properly generated and protects the field in question.
Name generated ignores the configured PropertyNameDecorator, resulting on an incorrect property to be ignored.
Removing the PropertyNameDecorator makes the issue inexistent, so in case of it not being necessary for the use case, removing it works as a workaround.