Split a function into two
This feels pretty messy. I'm not sure what the callstack looks like, but is it possible to introduce a second function for this (with shared code factored out) instead of overloading fetchPrimaryInviteLinks to handle two different scenarios?
Fri, Dec 1
Thu, Nov 30
Use a param object instead of two args for hash and holder to avoid the confusion between them
Accepting without review. What procedure did you use to rename all the types?
Wed, Nov 29
on the first rehydration this value could be undefined
Is it also true for other values from the keyserverInfo? Should we also handle them somehow?
Mon, Nov 27
Is the default_role column nullable at this point?
Fri, Nov 24
Use better error code
Thu, Nov 23
Move encrypting inside try-catch block