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.
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
Api #11
Conversation
@SebCorbin Is it usefull yet to add pagination? |
api/views.py
Outdated
|
||
class HistoryEntryListAPIView(ListAPIView): | ||
serializer_class = HistoryEntryListSerializer | ||
authentication_classes = [SessionAuthentication, ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we open history entries to everyone (question asked in chat)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pour les entrées d'historique, chacun doit implémenter sa propre vue (qui héritera d'une vue généraliste dans contrib\views.py) ==> Il faudra juste redéfinir la permission
Let's not paginate at the moment, even with 100 entries, it should be fast enough (and pagination would be hard on timelines) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good for me for now, we can handle the permissions question later (via a mixin maybe)
No description provided.