Should we add more convenient way of authorization with custom fields?

[mkhnuser]

I use DRF-simpleJWT for its simplicity and convenience, but there are a lot of moments, when one might want to change default token-obtain fields from username and password to, say, email and password, so you need to write your own CustomObtainTokenSerializer.

Can we solve this "problem" by adding extra functionality in simple-jwt settings?

[Andrew-Chen-Wang]

It's 5 extra lines of code. The configurations are mostly for stuff that's hard to simply override, and I personally like it that way. Though, your concerns have been raised before (I coined it as "flexibility").

FYI if your model's username field is "email", that's what it'll use. I'll leave this open for discussion.