Refactor rate-limit endpoint to use our pattern
The following discussion from !1900 (merged) should be addressed:
-
@Sporiff started a discussion: (+1 comment) As discussed with @georgkrause this addresses the OAPI generation issue. We should create a followup to actually refactor this at some point, but I don't think I will be able to do it as it's not my area of expertise.
The current implementation hurts the basic design pattern by DRF. We should gather the data in a view, bringing it to the right form with the serializers.