-
Notifications
You must be signed in to change notification settings - Fork 308
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
feat: storage calls without user session #836
Conversation
Codecov Report
@@ Coverage Diff @@
## feature/monorepo-refactor #836 +/- ##
=============================================================
- Coverage 77.11% 77.10% -0.02%
=============================================================
Files 72 72
Lines 4318 4320 +2
Branches 762 763 +1
=============================================================
+ Hits 3330 3331 +1
- Misses 952 953 +1
Partials 36 36
Continue to review full report at Codecov.
|
This change seems straightforward enough. @yknl do you want me to test this as an integration in my app specifically or are you confident it'll work there? |
@markmhx Yes, we can wait until you've had a chance to test it with your app, just want to make sure it resolves the issue for you. |
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.
Would love to see a test here but 👍
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.
This conditional doesn't seem to resolve the underlying problem with calling this function when no session user data is available.
This appears to be affecting the todos app as well hirosystems/todos#55 |
closing this for now. please re-open if you think this requires attention. if you re-open, please also suggest who could help resolve and carry it to the finish line 🙏🏼 |
This PR allows storage calls without having a signed in user session.
#802
For details refer to issue #123
Type of Change
Does this introduce a breaking change?
No
Are documentation updates required?
No
Testing information
Checklist
npm run test
passes