Incorrect Field Type in Response for GET /api/dcim/device-type(/{id}/) Model Schema

[jniec-js]

Deployment Type

Self-hosted

NetBox Version

v3.7.1

Python Version

3.11

Steps to Reproduce

1. Look at the API documentation for /api/dcim/device-types/{id}, on the demo site (https://demo.netbox.dev/api/schema/swagger-ui/#/dcim/dcim_device_types_retrieve) and inspect the Schema for DeviceType, see that front_image and rear_image are declared as strings
2. Use https://demo.netbox.dev/dcim/device-types/7/ as an example to test, a device_type that has no front or rear images associated with the object
3. Send an http GET request to /api/dcim/device-types/7/ using the netbox demo's swagger documentation website here: https://demo.netbox.dev/api/schema/swagger-ui/#/dcim/dcim_device_types_retrieve, click "try it out!", for the ID, enter in 7, click Execute
4. Observe that the response payload for front_image and/or rear_image is set to null and not an empty string despite the Model specifying "string" for the type and not specfying "nullable:true" on the field. See screenshots below:

Expected Behavior

I expected that the types in the response from the query would match what types are defined in the model.

Observed Behavior

We get back the wrong type in the response from the API when a front and/or rear image is not attached to a device_type.

[jeremystretch]

I expected that the types in the response from the query would match what types are defined in the model.

Please specify exactly what you expect to see in the specification for the field.

[jniec-js]

I would expect that the specification either say "nullable: true" or the response be an empty string for both fields.

[jeremystretch]

Can you point to an example of this elsewhere in the spec?

[jniec-js]

I see other fields in the same model as marked 'nullable: true'. Though these are objects, I am unsure if that matters for this or not though.