-
Notifications
You must be signed in to change notification settings - Fork 26
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
Sessions #412
Sessions #412
Conversation
Jyyjy
commented
Feb 13, 2024
- Git ignores the build. It makes PR's harder, and the build can still be included in release tags as artifacts.
- Adds httpSessionId and browserSessionID.
- Http session is essentially the same as sessionId, but is crypto-graphically unique.
- sessionId is left as is for users to set the application specific session id. In a 3.0.0 release, we can rename sessionId to serverSessionId and set the default to null. Or remove it entirely and allow users to set it as a custom field.
- browserSessionID is null be default unless using the web ext.
- The background script attempts to remap the session id's of tab events so they match the target tab's events. However some tab events happen before userale is initialized (e.g. tabs.onCreated). I'm sure there's a clever solution, but I'll leave that as a future issue.
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.
Alright, I am following this code.
Nonetheless, I'm ripping off the band-aid. It's time to add Doc strings top each function.
updateConfig(res); | ||
browserSessionId = JSON.parse(window.sessionStorage.getItem('userAleHttpSessionId')); |
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.
Is this the only place where the browserSessionId is set?
Why does this come from userAleHTTPSessionId?
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.
Yes it is the only place, and it comes from userAleHTTPSessionId because browser session is equivalent to the http session of the background page.