-
Notifications
You must be signed in to change notification settings - Fork 2.7k
adding CacheLocationChoices so clients don't need to worry about type widening #851
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
Conversation
running npm run endToEnd was broken, npm run test failed one time and passed the next, so seems like there might be a flaky test? i didn't want to change CacheLocation since probably a lot of users are relying on that so I just added a new enum that can be used instead. |
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.
Nice improvement, thanks for the contribution!
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.
lgtm. Thanks much for this improvement.
Merging as we got the team's approval. |
This ended up breaking surface configuration for cacheLocation, we will revert this PR and revisit the change in a future release. |
Revert "Merge pull request #851 from jodonnell/dev"
@jodonnell This was failing in typescript because it did not allow users to set string values for localstorage and sessionstorage and the enums weren't exported. Could you please test this in typescript and javascript to ensure the behavior is working correctly? You can open another PR, unfortunately I can't reopen this one. |
I will try to get this done in the near future. |
No description provided.