No ticket, trying to fix a bug in the notificationPanel of submissions where it was possible that the did-update was called before the mailSettings were fully loaded, resulting in lists with undefined entries which caused the save of the submission model to throw errors.
By making the did-update check for the mailSettings and running the restartable task again if not, we can ensure we never try to get the defaults before the mailSettings are fully loaded
Perhaps the getters (now using this.emailSettings?.) should not have that optional. If we attempt to call the getters at that stage we should stop instead of setting [undefined]
No ticket, trying to fix a bug in the notificationPanel of submissions where it was possible that the
did-updatewas called before themailSettingswere fully loaded, resulting in lists with undefined entries which caused the save of the submission model to throw errors.By making the
did-updatecheck for themailSettingsand running the restartable task again if not, we can ensure we never try to get the defaults before themailSettingsare fully loadedPerhaps the getters (now using
this.emailSettings?.) should not have that optional. If we attempt to call the getters at that stage we should stop instead of setting[undefined]