Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove nullable=True from CharField where not required #51

Open
SamStudio8 opened this issue Mar 6, 2021 · 0 comments
Open

Remove nullable=True from CharField where not required #51

SamStudio8 opened this issue Mar 6, 2021 · 0 comments
Assignees
@SamStudio8
Labels
enhancement New feature or request P:LOW An issue or feature that is not an obstacle to current work

Comments

@SamStudio8
Copy link
Owner

It is not Django best practice to allow for CharField to contain None and empty string unless absolutely necessary. This also is the root cause of None appearing in API serialiser responses.
@SamStudio8 SamStudio8 added enhancement New feature or request P:LOW An issue or feature that is not an obstacle to current work labels Mar 6, 2021
@SamStudio8 SamStudio8 self-assigned this Mar 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SamStudio8 SamStudio8

Labels
enhancement New feature or request P:LOW An issue or feature that is not an obstacle to current work
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SamStudio8