[GET] /api/v1/safes/:safeAddress - Nullable version field

[hectorgomezv]

Describe the bug
When retrieving a Safe info, null version field is returned, even though the OpenAPI definition for this service explicitly indicates SafeInfoResponse.version is not nullable.

To Reproduce
Steps to reproduce the behavior:

1. GET URL
2. Returns:

{
  "address": "0xa08826D91a104d31856F448190B346f077e3EABb",
  "nonce": 0,
  "threshold": 1,
  "owners": [
    "0x3955bDB84795fD30522F15A123C68792D3aAAf80"
  ],
  "masterCopy": "0x0000000000000000000000000000000000000000",
  "modules": [
    "0x3955bDB84795fD30522F15A123C68792D3aAAf80"
  ],
  "fallbackHandler": "0xf48f2B2d2a534e402487b3ee7C18c33Aec0Fe5e4",
  "guard": "0x0000000000000000000000000000000000000000",
  "version": null
}

Expected behavior
version field shouldn't contain null values.

[moisses89]

@hectorgomezv we are going to change the openapi doc to include nullable version.
Version is going to be null if the masterCopy address is not one of the deterministic known addresses.

[moisses89]

As I can see version is currently nullable on openApi from this commit
Which version of openApi are you using? https://redocly.com/docs/api-reference-docs/specification-extensions/x-nullable/

[hectorgomezv]

Yes, there's a misalignment between the OpenAPI and the inner validation schema. We need to fix the validation schema in the Client Gateway. Thanks for noticing @moisses89

[hectorgomezv]

Closing this, as this behavior is expected. Further changes must be made in the Client Gateway to accept nullable version fields.