-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated Account Setup and new Account Editing Functionality #35
Conversation
|
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #35 +/- ##
==========================================
+ Coverage 80.86% 81.68% +0.82%
==========================================
Files 30 32 +2
Lines 815 846 +31
==========================================
+ Hits 659 691 +32
+ Misses 156 155 -1
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
We still want to incorporate StanfordSpezi/SpeziAccount#24 EDIT: ✅ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the improvements @Supereg, great to see the new account module in the Template Application! 🚀
I only had a comment to reuse the account button across the different tabs to display it in a consistent position. Apart from this I am happy to see the PR being merged 👍
…Spezi#35) There is an upcoming release of SpeziAccount that restructures and simplifies account setup procedure. Further, it adds a new Account Overview that allows you to view and edit your active account details. While it might not be required for all projects, we currently force a user account (e.g. as the standard expects a user account for all operations) even if the user decides to log out. Furthermore, we restore test case functionality for some tests cases that broke due to the latest accessibility improvements in some dependencies. For more information see: * StanfordSpezi/SpeziAccount#7 * StanfordSpezi/SpeziFirebase#8 * Newly designed Account Setup experience * New Account Editing Functionality * Support complete removal of user data In code documentation was adjusted. Tests were updated to cover new vectors. By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md).
…Spezi#35) # Updated Account Setup and new Account Editing Functionality ## ♻️ Current situation & Problem There is an upcoming release of SpeziAccount that restructures and simplifies account setup procedure. Further, it adds a new Account Overview that allows you to view and edit your active account details. While it might not be required for all projects, we currently force a user account (e.g. as the standard expects a user account for all operations) even if the user decides to log out. Furthermore, we restore test case functionality for some tests cases that broke due to the latest accessibility improvements in some dependencies. For more information see: * StanfordSpezi/SpeziAccount#7 * StanfordSpezi/SpeziFirebase#8 ## ⚙️ Release Notes * Newly designed Account Setup experience * New Account Editing Functionality * Support complete removal of user data ## 📚 Documentation In code documentation was adjusted. ## ✅ Testing Tests were updated to cover new vectors. ## 📝 Code of Conduct & Contributing Guidelines By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md).
…Spezi#35) # Updated Account Setup and new Account Editing Functionality ## ♻️ Current situation & Problem There is an upcoming release of SpeziAccount that restructures and simplifies account setup procedure. Further, it adds a new Account Overview that allows you to view and edit your active account details. While it might not be required for all projects, we currently force a user account (e.g. as the standard expects a user account for all operations) even if the user decides to log out. Furthermore, we restore test case functionality for some tests cases that broke due to the latest accessibility improvements in some dependencies. For more information see: * StanfordSpezi/SpeziAccount#7 * StanfordSpezi/SpeziFirebase#8 ## ⚙️ Release Notes * Newly designed Account Setup experience * New Account Editing Functionality * Support complete removal of user data ## 📚 Documentation In code documentation was adjusted. ## ✅ Testing Tests were updated to cover new vectors. ## 📝 Code of Conduct & Contributing Guidelines By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md).
…Spezi#35) # Updated Account Setup and new Account Editing Functionality ## ♻️ Current situation & Problem There is an upcoming release of SpeziAccount that restructures and simplifies account setup procedure. Further, it adds a new Account Overview that allows you to view and edit your active account details. While it might not be required for all projects, we currently force a user account (e.g. as the standard expects a user account for all operations) even if the user decides to log out. Furthermore, we restore test case functionality for some tests cases that broke due to the latest accessibility improvements in some dependencies. For more information see: * StanfordSpezi/SpeziAccount#7 * StanfordSpezi/SpeziFirebase#8 ## ⚙️ Release Notes * Newly designed Account Setup experience * New Account Editing Functionality * Support complete removal of user data ## 📚 Documentation In code documentation was adjusted. ## ✅ Testing Tests were updated to cover new vectors. ## 📝 Code of Conduct & Contributing Guidelines By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md).
…Spezi#35) There is an upcoming release of SpeziAccount that restructures and simplifies account setup procedure. Further, it adds a new Account Overview that allows you to view and edit your active account details. While it might not be required for all projects, we currently force a user account (e.g. as the standard expects a user account for all operations) even if the user decides to log out. Furthermore, we restore test case functionality for some tests cases that broke due to the latest accessibility improvements in some dependencies. For more information see: * StanfordSpezi/SpeziAccount#7 * StanfordSpezi/SpeziFirebase#8 * Newly designed Account Setup experience * New Account Editing Functionality * Support complete removal of user data In code documentation was adjusted. Tests were updated to cover new vectors. By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md).
…Spezi#35) There is an upcoming release of SpeziAccount that restructures and simplifies account setup procedure. Further, it adds a new Account Overview that allows you to view and edit your active account details. While it might not be required for all projects, we currently force a user account (e.g. as the standard expects a user account for all operations) even if the user decides to log out. Furthermore, we restore test case functionality for some tests cases that broke due to the latest accessibility improvements in some dependencies. For more information see: * StanfordSpezi/SpeziAccount#7 * StanfordSpezi/SpeziFirebase#8 * Newly designed Account Setup experience * New Account Editing Functionality * Support complete removal of user data In code documentation was adjusted. Tests were updated to cover new vectors. By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md).
Updated Account Setup and new Account Editing Functionality
♻️ Current situation & Problem
There is an upcoming release of SpeziAccount that restructures and simplifies account setup procedure. Further, it adds a new Account Overview that allows you to view and edit your active account details.
While it might not be required for all projects, we currently force a user account (e.g. as the standard expects a user account for all operations) even if the user decides to log out.
Furthermore, we restore test case functionality for some tests cases that broke due to the latest accessibility improvements in some dependencies.
For more information see:
⚙️ Release Notes
📚 Documentation
In code documentation was adjusted.
✅ Testing
Tests were updated to cover new vectors.
📝 Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: