Open dvstans opened 3 years ago
What changed, or what functionality or use case warrants this now?
The original DB implementation made assumptions about aliases before the ability to set a context was added (i.e. working as a project). I think this may have been fixed, but need to review the code to be sure.
There is now a need to resolve aliases based on users other than the authenticated client - and for projects. The support library methods for this work only for the authenticated user.