Wrong integer format in openapi spec for read only big integers

[poroh]

Rest framework removes min_value and max_value kwargs for readonly fields:

django-rest-framework/rest_framework/serializers.py

Line 1380 in 8637b3d

'max_length', 'min_value', 'max_value', 'validators', 'queryset'

But drf-spectacluar uses these values to detect when format: int64 should be added:

Here it sets minimum and maximum by these values:
https://github.com/tfranzel/drf-spectacular/blob/5734744545bd0c4801c4c010d13edc77328fd412/drf_spectacular/openapi.py#L932

And here adds format if minimum or maximum are outside integer range:
https://github.com/tfranzel/drf-spectacular/blob/5734744545bd0c4801c4c010d13edc77328fd412/drf_spectacular/openapi.py#L846

I'm not sure how this should work. Writing to rest-framework because it first erases information about integer range.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[auvipy]

I'm not sure what are you trying to explain. DRF has decided to move out of its built in schema generator.

[poroh]

I'm not sure what are you trying to explain. DRF has decided to move out of its built in schema generator.

It is hard to answer to this comment. I've explained everything in comment above. I can only repeat myself.

• django removes min_value / max_value properties for read-only fields
• these properties are used by DRF to decide to use / not not use format: int64 in openapi spec.

Therefore for them no way to detect if this format can be used for read only fields. I assume that somebody from django need to talk to somebody to DRF and decide how to fix this.