When registering a CharField for translation, the extra language fields that are created have null=True. Django explicitly recommends against that. According to Django's recommended practices, the fields should be nullable and store empty strings by default. If someone for some reason needs to have nullable language fields, they should have to explicitly set some extra configuration for that to happen. Currently not only is this behavior not the default, there seems to be no available settings that I can configure in order to get the desired behavior.
When registering a CharField for translation, the extra language fields that are created have
null=True
. Django explicitly recommends against that. According to Django's recommended practices, the fields should be nullable and store empty strings by default. If someone for some reason needs to have nullable language fields, they should have to explicitly set some extra configuration for that to happen. Currently not only is this behavior not the default, there seems to be no available settings that I can configure in order to get the desired behavior.