Add support for creating long int ( integer, int64) fields.

[dnit]

Feature Request

Lack of support for long int field via django Fields and rest_framework Serializers

Currently there is no concise way of creating long integer field in swagger spec for models.BigAutoField
The only way is to override the view with swagger_auto_schema.

Describe the solution you'd like

Should we add this support inherently via model_field_to_basic_type mapping here. Although this would only add support for Django models but not via DRF serializers because there is only serializers.IntegerField and no equivalent of models.BigAutoField. I agreed I can raise a PR for the same and open to suggestions for DRF serializer.

[andrewkoltsov]

It appears the underlying issue originates from Django Rest Framework's serializer fields (https://www.django-rest-framework.org/api-guide/fields/#integerfield), specifically because DRF's IntegerField does not distinguish between Django's BigIntegerField and IntegerField (https://github.com/encode/django-rest-framework/blob/master/rest_framework/serializers.py#L909). To effectively implement your requested enhancement, we should first propose adding explicit support for BigIntegerField to DRF serializers. This way, the Swagger specification generation can inherently differentiate between standard integers and long integers without the need for manual schema overrides.

But Django Rest Framework issues are closed because encode/django-rest-framework#9560 (comment)

[JoelLefkowitz]

@andrewkoltsov thanks for the explanation it's really helpful. I'm had heard there was drama on the DRF repo but I had no idea it got that bad. Looks like there's no point even trying to put forward a PR to them at the moment. On our side we could add the support at the model level as @dnit suggested, unless someone can think of a creative way around this?

[andrewkoltsov]

@JoelLefkowitz I used Cursor to generate the code changes for #924, but the tests are failing. From what I understand, this is because DRF doesn’t differentiate between BigIntegerField and IntegerField.

[dnit]

@JoelLefkowitz @andrewkoltsov Thanks for acknowledging. The models solution would be straight forward for Django. But, I am not sure what can be done for DRF serializers and I am not even sure if DRF would even acknowledge this as an enhancement required for DRF, although I have started a discussion here , keeping my hopes low 🤞. One hackish way I can think of on top of my head is trying to use the label field for IntegerField and if it is something like long or longint but this would be very 💩 since that's not what label is meant for, or if there is better way around it. I really wish someday DRF provides a cleaner way of differentiation.

[andrewkoltsov]

Good luck @dnit ,
all we need from DRF is:

class BigIntegerField(IntegerField):
    pass

and

models.BigIntegerField: BigIntegerField,