You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If all of the properties of a model are optional (?) and using ArmPatchResourceSync/Async, the emitter will not define and emit a new Update model to represent the PATCH operation. This results in what I think is improper spec (or, at least, azure-openapi-validator complains about it).
In the above playground, the patch expects the EmployeeUpdate which contains EmployeeProperties and the ManagedServiceIdentityUpdate. However, the properties of EmployeeProperties are all create/read-only properties. Removing the nullability of one of the properties--say, age--will instead prompt the emittance of EmployeeUpdate containing EmployeePropertiesUpdate, which in turn is defined with no properties (as nothing from EmployeeProperties should be able to be updated.
Not sure if this improper definition by us, though. We're running into RPC-Patch-V1-02 and RPC-Patch-V1-10 because of this.
The text was updated successfully, but these errors were encountered:
If all of the properties of a model are optional (
?
) and usingArmPatchResourceSync
/Async
, the emitter will not define and emit a new Update model to represent the PATCH operation. This results in what I think is improper spec (or, at least, azure-openapi-validator complains about it).Playground Link
In the above playground, the patch expects the
EmployeeUpdate
which containsEmployeeProperties
and theManagedServiceIdentityUpdate
. However, the properties ofEmployeeProperties
are all create/read-only properties. Removing the nullability of one of the properties--say, age--will instead prompt the emittance ofEmployeeUpdate
containingEmployeePropertiesUpdate
, which in turn is defined with no properties (as nothing fromEmployeeProperties
should be able to be updated.Not sure if this improper definition by us, though. We're running into RPC-Patch-V1-02 and RPC-Patch-V1-10 because of this.
The text was updated successfully, but these errors were encountered: