Codecov Report

Merging #18 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #18   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines           70        75    +5     
  Branches        16        17    +1     
=========================================
+ Hits            70        75    +5     

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bd0a73e...9c0e15f. Read the comment docs.

Another potential solution would be to initially return null until we had the chance to check the localStorage, that way you can employ conditional rendering to avoid the "flicker", but none of this feels great for non-SSR applications :(

Hey @thorsten-stripe! Thanks a lot for bringing this up and looking into it. Returning undefined initially and then updating in the first useEffectcall is actually what a previous version of the library did... and someone got rightfully confused by it and opened an issue 😅 It's been fixed since then. As you say, that wouldn't feel great, neither returning defaultState.

I think this use case would be covered by adding support for async storages, which is a feature that has been asked for. If the API of the hooks were async, returning null/undefined in the first render would no longer feel confusing (it would return a loading boolean as well, similar too Apollo hooks if you're familiar with those; or use a state machine maybe). Do you think something like that would work for you?

Thanks, @soyguijarro, yes, I think the async approach and the loading boolean would solve this, thanks :) I'll close this one out.