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
At the moment, we manage notification settings via a custom UserMetaDataManager that listens to changes in the User document in Firestore and record information like organization affiliation and notification preferences. However, with the new version of SpeziAccount, this user meta might lend itself to being represented as @ApplicationKeys instead.
Solution
See if @ApplicationKeys would be a good fit for the use meta data, and if so replace the UserMetaDataManager with these macros. Update the settings views in the Account Sheet to use built in SpeziAccount views.
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct and Contributing Guidelines
The text was updated successfully, but these errors were encountered:
Problem
At the moment, we manage notification settings via a custom UserMetaDataManager that listens to changes in the User document in Firestore and record information like organization affiliation and notification preferences. However, with the new version of SpeziAccount, this user meta might lend itself to being represented as @ApplicationKeys instead.
Solution
See if @ApplicationKeys would be a good fit for the use meta data, and if so replace the UserMetaDataManager with these macros. Update the settings views in the Account Sheet to use built in SpeziAccount views.
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: