-
Notifications
You must be signed in to change notification settings - Fork 1
PER-10096-archive-invitations[waiting on BE fix] #577
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
PER-10096-archive-invitations[waiting on BE fix] #577
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #577 +/- ##
==========================================
+ Coverage 45.17% 45.51% +0.33%
==========================================
Files 370 370
Lines 11255 11272 +17
Branches 1855 1858 +3
==========================================
+ Hits 5085 5130 +45
+ Misses 6001 5974 -27
+ Partials 169 168 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
1946df0 to
33b173e
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.
Code looks good -- ready for QA testing!
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.
This does not appear to be working as described. I invited an existing account B to be a member of my archive from account A. I got an email from account A to account B with a link, then copy/pasted it to a browser window where account B was logged in. I was not directed to pending archives. See attached video:
- account A = [email protected]
- account B = [email protected]
- URL = https://dev.permanent.org/app/pr/manage?fullName=Um9iZXJ0IFRlc3QxMTUw&primaryEmail=cm9iZXJ0K3BybW50dHN0MTE1MEBwZXJtYW5lbnQub3Jn
I did not attempt to QA this for a member invite to a non-existant account since that should take the new account through onboarding to accept the invite.
Screen.Recording.2025-07-21.at.1.09.02.PM.mov
|
@omnignorant you are right, when I implemented this the email system was not working on my side. Should I implement this only on the frontend or should we change the backend aswell with the correct url taking you to the pending archive? The curent email url only has 2 parameters which maybe in the future could also have other purposes, and I think the frontend should not handle this on its own, but I might be wrong and I am open to suggestions. CC: @slifty @liam-lloyd |
I think it does make sense for the URL to specify which tab in the modal should be selected, and to update the link the backend includes in this email to reflect that. |
|
@liam-lloyd this is how the url looks like to get redirected to pending archives: https://local.permanent.org/app/(private/0004-0006/75//dialog:archives/pending) |
|
Bumping this @crisnicandrei and @omnignorant -- it would be great to rebase this and get it over the edge if at all possible. It sounds like there may be open questions about desired functionality? |
067c535 to
1a2411f
Compare
PER-10096-archive-invitations -Create new route for archives dialog -Redirect that new route based on the url to the pending archives dialog
1a2411f to
2528c26
Compare
|
This is waiting on a backend fix, which @cecilia-donnelly is going to be taking on at some point. |
|
This is the backend ticket: https://permanent.atlassian.net/browse/PER-10291. We talked to @omnignorant about it and he'd like to write better requirements better we work on it (in particular drafting the email text). |
How to test: