M2-6212: Allow direct linking to activity

[sultanofcardio]

📝 Description

🔗 Jira Ticket M2-6212

This change allows directly linking to an activity by wrapping the < AppletDetailsPage /> component in an <AuthorizationGuard />. I also created a new reusable component called <LoginWithRedirect /> that, in combination with the <AuthorizationGuard />, automatically takes the user to the login page if they try to access a page while unauthenticated, and then redirects them to wherever they originally tried to access.

The URL takes the format https://localhost:5173/protected/applets/{appletId}?startActivityOrFlow={activityOrFlowId}

This lands the user on the page of a specific applet, and immediately starts the activity/flow specified by the ID.

I contemplated making this <LoginWithRedirect /> component the default fallback for the <AuthorizationGuard />, as that made sense to me but I opted not to do that at this time. Let me know if you think that's something worth doing.

After initial review, I ultimately decided to make the <LoginWithRedirect /> component the default fallback for the <AuthorizationGuard />

I went back and forth on this but eventually decided to leave the <AuthorizationGuard /> component without a default fallback, and avoid increasing the scope of the PR.

I also removed the isInvitationFlow parameter from the useOnLogin hook, and chose instead to rely on the existence of the backRedirectPath parameter, since it seems that's what isInvitationFlow was meant to do anyway.

📸 Screenshots

Before this change, if you tried to directly access an activity by URL, you would be taken to the applets screen after authenticating

before-2.mov

Now, you'll be redirected to the activity, provided the URL parameters you passed are valid

after-2.mov

🪤 Peer Testing

Warning

This won't work using the preview environment due to the way it currently handles client side routing. You must test this locally

First authenticate, and navigate to an activity. Then copy the URL from the browser, log out, paste the URL again and go. You should be asked to log in, after which you are taken back to the activity

[aws-amplify-us-east-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-431.d15zn9do8xbzga.amplifyapp.com

[farmerpaul]

Looks great @sultanofcardio, I like your changes. I made one suggestion and had a minor question.

Just a reminder to update the JIRA task description & AC to align with the new requirements before passing it over to QA (I'd probably just do it myself rather than wait for Suzanne, but your call).

[moiskillnadne]

All current changes look good. But when I tested it locally I found one bug. The root of the issue is when we go directly to activity we skip the step where we set the activity group in the store. The activity group data contains info about flow, timestamps and so on. When we want to submit our answers we use some data from the activity group state. So we should fix it somehow because without this data we can`t send answers.

The issue

The slice in the store

The place in the code where we use this data. [/src/widgets/ActivityDetails/model/hooks/useAnswers.ts]

[sultanofcardio]

@moiskillnadne thanks for the review. I believe I've fixed the error you identified. Please review again

[moiskillnadne]

Good. Now it`s working. I left one comment about the console log but generally approve. Thank you!