remove omitempty from booleans on Oauth2Configuration

[autom8ter]

Having omitempty on the booleans of the OAuth2Configuration object means that requireClientAuthentication & generateRefreshTokens can never be set to false in API requests. When either are set to false, they are omitted from the request body and FA defaults them to true.

[robotdan]

This file is generated. If we incorporate this change, would the correct change be to remove omitempty for all bool types across the entire domain?

[autom8ter]

Yes, that would be the right move. It's important to explicitly set false booleans on many domain objects.

[robotdan]

Great, thanks @autom8ter - will be be backwards compatible as far as you know?

Ok, for reference here is the code I'll be modifying.

https://github.com/FusionAuth/fusionauth-client-builder/blob/c0489c9f57a6861d94368ce253d91b7d0279aaff/src/main/client/go.domain.ftl#L91

[autom8ter]

yes, it will be backwards compatible 👍

[robotdan]

See commits
FusionAuth/fusionauth-client-builder@19dbfe7
25495fe

[autom8ter]

@robotdan this looks good. Id assume "string" and "int" fields would need this too(0 & "" may be valid inputs for certain requests) but this is good for now.

[robotdan]

Thanks @autom8ter - we lean on our community experts in each language domain for this type of input. It is appreciated.

If you run into this issue with other data types, please let us know!