Do you want to request a feature or report a bug?
Both
What is the current behavior?
I preload the store with user profile data, SSR the page (works fine), then on client action @@reactReduxFirebase/LOGIN resets my profile data and later fills it with @@reactReduxFirebase/SET_PROFILE which causes a flicker when page loads.
What is the expected behavior?
When updating state for @@reactReduxFirebase/LOGIN action perform a validation if the profile contains keys isEmpty and isLoaded set to false and true respectively, in which case it would not clean profile
(Maybe add a special key for preloaded profile and remove that key if present?)
I may be doing this wrong, but documentation on SSRing is not very clear. It doesn't mention auth properties like currentUser and what not
Do you want to request a feature or report a bug?
Both
What is the current behavior? I preload the store with user profile data, SSR the page (works fine), then on client action
@@reactReduxFirebase/LOGINresets my profile data and later fills it with@@reactReduxFirebase/SET_PROFILEwhich causes a flicker when page loads.What is the expected behavior? When updating state for
@@reactReduxFirebase/LOGINaction perform a validation if the profile contains keysisEmptyandisLoadedset tofalseandtruerespectively, in which case it would not clean profile (Maybe add a special key for preloaded profile and remove that key if present?)I may be doing this wrong, but documentation on SSRing is not very clear. It doesn't mention auth properties like
currentUserand what not