With CRUD API approach, where you replace at update, it's very inconvenient when the SDK is not reflecting the API.
casdoor/casdoor@3cb9df3
The change isn't even mentioned in swagger v1.503.0
The change isn't backward compatible, not when the client doesn't know that, and sends back the field implicitly with zero-value.
With CRUD API approach, where you replace at update, it's very inconvenient when the SDK is not reflecting the API.
casdoor/casdoor@3cb9df3
The change isn't even mentioned in swagger v1.503.0
The change isn't backward compatible, not when the client doesn't know that, and sends back the field implicitly with zero-value.