:memo: Made notes for tomorrow's meet with TOJ

frontend/src/views/OnboardingView.vue

@@ -47,6 +47,26 @@ let sessionToken = null
 let accessToken = null
 // import savesurveybyprofileid - call it on submit
 // paginate to save every steps answers
+
+/* BRIAN'S NOTE: 
+I'll need help here. The logic is getting confusing.
+
+    1.  Right now both a session and access token are issued 
+        (session via Auth.vue, access from VerifyView.vue).
+
+    2.  There is also a hashedEmail object on the backend's app state:
+        {
+            hashedEmailString: expiration_in_milliseconds,
+            anotherhashedEmailString: expiration_in_milliseconds,
+        }
+
+    3.  The session, access tokens all have jwt expirations as well as cookie expirations
+
+    4.  Additionally, we have an expiration on each hashedEmail string...
+    5.  All the data points to check are here... 
+        I just can't quite think straight as of 07/09/2023 at 01:53:22
+*/
+
 export default {
     name: 'OnboardingView',
     components: {
@@ -89,6 +109,7 @@ export default {
         if (sessionData) {
             this.userEmail = sessionData.payload.email
             this.emailIsRegistered =
+                // QUESTION: Would this logic also be needed in VerifyView??
                 await this.authenticator.checkIfEmailIsRegistered(
                     this.userEmail,
                 )

frontend/src/views/VerifyView.vue

@@ -40,6 +40,7 @@ export default {
                 ? cookies[`${cookieKey}`]
                 : undefined
         },
+        // QUESTION: This will likely be needed in OnboardingView.vue
         async getAccessToken(payload) {
             const accessToken = await this.authenticator.getJwt({
                 payload,