Is your feature request related to a problem? Please describe.
There are only hot, fresh and rising community subscriptions available. Top and views count should be available too.
Describe the solution you'd like
Add new data to database. Possible solution to associate sections with tag_orders table. Better to rename it to orders. Add parser in bot commands.
Easiest way is to add orders for communities: views_count (views_count) and likes_count (top) and make user to subscribe to it.
These orders are available only for fresh section and not for any other.
Example of request:
1) api/v2/timeline/community/anime/fresh?order_by=likes_count&page=1
2) api/v2/timeline/community/anime/fresh?order_by=views_count&page=1
In help template add message:
Fresh section has orders:
top
views_count
Also add validation for orders to be available only for fresh section.
Is your feature request related to a problem? Please describe. There are only hot, fresh and rising community subscriptions available. Top and views count should be available too.
Describe the solution you'd like Add new data to database. Possible solution to associate sections with tag_orders table. Better to rename it to orders. Add parser in bot commands.
Easiest way is to add orders for communities: views_count (views_count) and likes_count (top) and make user to subscribe to it. These orders are available only for fresh section and not for any other.
Example of request:
1) api/v2/timeline/community/anime/fresh?order_by=likes_count&page=1
2) api/v2/timeline/community/anime/fresh?order_by=views_count&page=1
In help template add message:
Also add validation for orders to be available only for fresh section.
Describe alternatives you've considered None
Additional context None