-
Notifications
You must be signed in to change notification settings - Fork 101
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
Add a WebRegistrationScreen (not included in the flow yet). #3281
Conversation
8b27605
to
0d164d1
Compare
Log
|
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## develop #3281 +/- ##
===========================================
- Coverage 77.76% 77.31% -0.46%
===========================================
Files 725 731 +6
Lines 58788 59041 +253
===========================================
- Hits 45716 45647 -69
- Misses 13072 13394 +322
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Couple of comments but lgtm 👍
.../Sources/Screens/Authentication/WebRegistrationScreen/WebRegistrationScreenCoordinator.swift
Show resolved
Hide resolved
Super weird, I was wondering why we did that and I think we just copied it from Riot. Why we did it like that there beats me. We should leave a todo in the code to get rid of this one and rewrite the other. |
Quality Gate passedIssues Measures |
This PR adds a screen that can perform registration using a helper URL. A follow-up PR will be made that includes the changes to the flow.
Note: This screen is based upon the login screen which also seems to include the logic in the Coordinator instead of the ViewModel. As it is temporary it didn't seem worth re-writing.