d1fa01fcc5
fix(avs): towards #117 update if current value is Nothing even if oldval == newval
...
Damit sollten zumindest die ganzen NULL Fälle bein einem neuen Update erledigt sein. Unklar, wo diese aber herkamen.
2024-08-02 16:13:09 +02:00
507a7e02fc
fix(avs): using firm superior as UserEmail is a no-go due to uniqueness constraints
...
Thus, we do not save the firm superior as `UserEmail` any more. The firm superior email is still used as a fallback for `CompanyEmail` which in turn is used as a fallback email, if a `CompanyUser` has no valid email at all.
2024-07-31 15:03:26 +02:00
43f5c5f485
fix(avs): fix #173 by not using firm superior email as display email
...
Instead, a valid firm superior email is used as `UserEmail` so that it can be used as a fallback address.
2024-07-31 14:16:40 +02:00
9e2f2214ce
fix(avs): do not associate users by AvsInfoPersonEmail
2024-07-02 15:27:56 +02:00
3dfc7f8c8b
fix(doc): fix erroneous unintentional haddock annotations
2024-06-27 16:48:47 +02:00
e4fa1ddd68
fix(avs): priority for picking primary email demote superior
2024-06-25 15:54:55 +02:00
822c43c8a7
fix(avs): fix type causing avs surname upate not working
2024-06-21 08:45:16 +00:00
ab5e432b77
refactor(avs): use associated type family to consistently produce CheckUpdate
2024-06-19 15:10:23 +02:00
a6d0105903
fix(avs): fix rare avs update bug involving values optional in avs but compulsory in user entity
2024-06-17 17:50:41 +02:00
