-
Notifications
You must be signed in to change notification settings - Fork 286
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
Setup completion tracking #9052
Conversation
Build files for 715169e have been deleted. |
Size Change: +5.25 kB (+0.31%) Total Size: 1.67 MB
ℹ️ View Unchanged
|
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 @zutigrm , this is quite close I think, just a few things to update and it should be good to go 👍
@aaemnnosttv Thanks, I updated the PR |
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 @zutigrm, just a few last things.
beforeAll( () => { | ||
setStorageOrder( [ 'localStorage', 'sessionStorage' ] ); | ||
} ); |
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.
Why are we setting this to prefer localStorage
? I don't think it should be necessary to set/change.
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.
Since by default order it is setting sessionStorage
for the storageBackend
backend. And we are running this in test environment it made more sense to me to use localStorage
for stability, even our storage mechanism prefers to use sessionStorage
for some reason in these tests.
I wrote the tests to use localStorage
in expect
checks, but it was failing, and after digging I found that it was using sessionStorage
instead, so I had to change the order to use localStorage
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.
Both are mocked so one shouldn't be more stable than another. It sounds like it was failing from checking the wrong storage but we shouldn't even need to be specific about which one and instead use our getStorage
utility.
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.
Great, thanks @zutigrm 👍
Summary
Addresses issue:
Relevant technical choices
PR Author Checklist
Do not alter or remove anything below. The following sections will be managed by moderators only.
Code Reviewer Checklist
Merge Reviewer Checklist