You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Profile model needs a new field called order. This will be an IntegerField that is unique with the model's km_user field. We need to make sure this field is correctly populated when a new profile is created.
We need a serializer that takes an array of IDs and sets the order field from the data
We need a view that exposes the ordering serializer
Items 2 and 3 would ideally be generic solutions because we also need to apply this ordering logic to profile topics and profile items in the future.
As far as modifying the order goes, I think our best option is a PUT request to the list endpoint with an array of the profiles' primary keys in the desired order. The collections we're dealing with are small enough that it's not a pain to specify the order of the entire collection, and our traffic is low enough that I don't think concurrent requests will be a problem.
Feature Proposal
Profiles need to be able to be reordered manually. The default profile to load should be the first in the list.
We should add sort_by field to determine the order the profiles appear and remote the default profile field.
The text was updated successfully, but these errors were encountered: