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

Fix name of selectors

Browse Source
This commit is contained in:
Radoslav Georgiev 2021-09-25 19:27:15 +03:00
parent 7886bfa432
commit ad51865d25
No known key found for this signature in database
GPG Key ID: 0B7753A4DFCE646D
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -452,15 +452,15 @@ A selector follows the same rules as a service.
For example, in a module `<your_app>/selectors.py`, we can have the following: For example, in a module `<your_app>/selectors.py`, we can have the following:
```python ```python
def users_list(*, fetched_by: User) -> Iterable[User]: def user_list(*, fetched_by: User) -> Iterable[User]:
user_ids = users_get_visible_for(user=fetched_by) user_ids = user_get_visible_for(user=fetched_by)
query = Q(id__in=user_ids) query = Q(id__in=user_ids)
return User.objects.filter(query) return User.objects.filter(query)
``` ```
As you can see, `users_get_visible_for` is another selector. As you can see, `user_get_visible_for` is another selector.
You can return querysets, or lists or whatever makes sense to your specific case. You can return querysets, or lists or whatever makes sense to your specific case.