HackSoftware/Django-Styleguide
1
1
Fork 0
mirror of https://github.com/HackSoftware/Django-Styleguide.git synced 2025-03-12 14:55:47 +03:00
Code Issues Packages Projects Releases Wiki Activity

Fix a typo

Browse Source 
- Fixes #167
This commit is contained in:
Radoslav Georgiev 2025-02-19 10:27:12 +02:00
parent dc3f88de76
commit 2396ac537d
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -293,7 +293,7 @@ This also plays well with Django admin, because the forms used there will trigge
As proposed in [this issue](https://github.com/HackSoftware/Django-Styleguide/issues/22), if you can do validation using [Django's constraints](https://docs.djangoproject.com/en/dev/ref/models/constraints/), then you should aim for that. As proposed in [this issue](https://github.com/HackSoftware/Django-Styleguide/issues/22), if you can do validation using [Django's constraints](https://docs.djangoproject.com/en/dev/ref/models/constraints/), then you should aim for that.
Less code to write, less to code to maintain, the database will take care of the data even if it's being inserted from a different place. Less code to write, less code to maintain, the database will take care of the data even if it's being inserted from a different place.
Lets look at an example! Lets look at an example!