json-api-dotnet
Reuse schema for POST and PATCH versions of resource request object
Currently the integration always uses a different resource object for patching and posting purposes in schema generation.
There exist two different schemas for posting and patching a resource object because in principle their set of attributes may differ as a result of attribute capability configurations. However, if the attribute capabilities are configured in such a way that there is no difference, there is no need to distinguish between ResourcePostRequestObject and ResourcePatchRequestObject. We can then introduce an optimisation by using ResourceRequestObject for both.
It needs to be carefully if the effect of such optimization on the usage of a generated client is desired: changing attribute capabilities could lead to generated types changing or appearing in an unexpected way.
