-
Notifications
You must be signed in to change notification settings - Fork 27
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
✨ Invitations to register to product 🚨 #4739
✨ Invitations to register to product 🚨 #4739
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #4739 +/- ##
=========================================
- Coverage 81.8% 81.3% -0.6%
=========================================
Files 1162 524 -638
Lines 48514 26592 -21922
Branches 748 198 -550
=========================================
- Hits 39704 21628 -18076
+ Misses 8651 4914 -3737
+ Partials 159 50 -109
Flags with carried forward coverage won't be shown. Click here to find out more.
|
08dbb5d
to
05fe78b
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
05fe78b
to
036bdc7
Compare
5ba7b7e
to
7bf2baf
Compare
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.
Just wanted to double check with you: Currently when this signal is emited: SIGNAL_ON_USER_CONFIRMATION
the default wallet is created for that user in that product, this will be still valid in this new approach of inviting users that are already in the DB to the new product? Thanks
Update: just checked, that yes, the function notify_user_confirmation
would still be called which is good, so the wallet should be created 👍
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.
Looking good thanks! Looking forward for the next PR for #4776 , then we can modify the hardcoded s4l
in the socketio connection
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.
Looks good, there are some asserts looking out of place to me
services/web/server/src/simcore_service_webserver/login/_auth_api.py
Outdated
Show resolved
Hide resolved
services/web/server/src/simcore_service_webserver/login/handlers_registration.py
Show resolved
Hide resolved
services/web/server/src/simcore_service_webserver/login/handlers_registration.py
Show resolved
Hide resolved
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.
Thanks!
services/web/server/src/simcore_service_webserver/login/handlers_registration.py
Show resolved
Hide resolved
Code Climate has analyzed commit d9634d9 and detected 0 issues on this pull request. View more on Code Climate. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
What do these changes do?
Invitation links allows a user to register a new account. The invitation is bound to an
email
and now also to aproduct
. That means thatNOTE that this PR addresses invitations BUT login bound to product is coming in a subsequent PR.
Highlights
webserver.invitations
plugininvitation.product == current_product
webserver.login
plugin/docs/coding-conventions.md
)list_products
Related issue/s
invitations
service was updated to account forproducts
How to test
Driving test is
services/web/server/tests/unit/with_dbs/03/invitations/test_invitations.py
DevOps
None