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
Currently, the collection retrieved by ProxiedUserDetails.getProxiedUsers (which are all users) has the final caller as the first entry followed by the entities in the call chain in the order that they happened. This creates some minor complexity in finding the primaryUser and in explaining this order to others.
Modify the places where ProxiedUserDetails iws created such that the proxied entities are first (already in chronological order) and the final caller is last ..... making it also in chronological order
The text was updated successfully, but these errors were encountered:
billoley
changed the title
Maintain the list of users in ProxiedUserDetails in a more sensible order
Maintain the list of users in ProxiedUserDetails in chronological (call-time) order
Apr 5, 2022
…cal (call-time) order (#12)
* re #11 Maintain the list of users in ProxiedUserDetails in chronological (call-time) order
* re #11 fix comment, simplify logic in orderProxiedUsers
* re #11 code formatting
Currently, the collection retrieved by ProxiedUserDetails.getProxiedUsers (which are all users) has the final caller as the first entry followed by the entities in the call chain in the order that they happened. This creates some minor complexity in finding the primaryUser and in explaining this order to others.
Modify the places where ProxiedUserDetails iws created such that the proxied entities are first (already in chronological order) and the final caller is last ..... making it also in chronological order
The text was updated successfully, but these errors were encountered: