-
Notifications
You must be signed in to change notification settings - Fork 894
refactor: Refactor auth provider #5782
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
Changes from 13 commits
244845f
b83f9c2
528892f
9f0e0ee
1714ca5
884dac7
970e1a5
6e572e3
6442b3a
5747590
7768e95
1173d16
ea4300b
d8826c3
e12f437
9e7a875
3e589f1
dce50e3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,29 +1,26 @@ | ||
import CssBaseline from "@material-ui/core/CssBaseline" | ||
import ThemeProvider from "@material-ui/styles/ThemeProvider" | ||
import { AuthProvider } from "components/AuthProvider/AuthProvider" | ||
import { FC } from "react" | ||
import { HelmetProvider } from "react-helmet-async" | ||
import { BrowserRouter as Router } from "react-router-dom" | ||
import { AppRouter } from "./AppRouter" | ||
import { ErrorBoundary } from "./components/ErrorBoundary/ErrorBoundary" | ||
import { GlobalSnackbar } from "./components/GlobalSnackbar/GlobalSnackbar" | ||
import { dark } from "./theme" | ||
import "./theme/globalFonts" | ||
import { XServiceProvider } from "./xServices/StateContext" | ||
|
||
export const App: FC = () => { | ||
return ( | ||
<Router> | ||
<HelmetProvider> | ||
<ThemeProvider theme={dark}> | ||
<CssBaseline /> | ||
<ErrorBoundary> | ||
<XServiceProvider> | ||
<AppRouter /> | ||
<GlobalSnackbar /> | ||
</XServiceProvider> | ||
</ErrorBoundary> | ||
</ThemeProvider> | ||
</HelmetProvider> | ||
</Router> | ||
<HelmetProvider> | ||
<ThemeProvider theme={dark}> | ||
<CssBaseline /> | ||
<ErrorBoundary> | ||
<AuthProvider> | ||
<AppRouter /> | ||
<GlobalSnackbar /> | ||
</AuthProvider> | ||
</ErrorBoundary> | ||
</ThemeProvider> | ||
</HelmetProvider> | ||
) | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
import { useActor, useInterpret } from "@xstate/react" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we should move all Providers into a provider or state directory instead of them living mixed in with our components. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Actually I would call it There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I see Provider being used more broadly in community but I'm ok with Context too. About where to put them, I think a context directory is good! There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As long as we establish a consistent pattern, I'm not too picky! There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Totally |
||
import { createContext, FC, PropsWithChildren, useContext } from "react" | ||
import { authMachine } from "xServices/auth/authXService" | ||
import { ActorRefFrom } from "xstate" | ||
|
||
interface AuthProviderContextValue { | ||
authService: ActorRefFrom<typeof authMachine> | ||
} | ||
|
||
const AuthProviderContext = createContext<AuthProviderContextValue | undefined>( | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. NIT: I would probably just name this There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. But there is a difference. The AuthContext is the one created from React.createContext, and the Provider is the wrapper around it that define the values like data and additional functions There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I get the difference - I would name it There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ahh I see. But in this case the Context is being used directly. We can think like Material UI that has a wrapper around the their theme context and named it ThemeProvider as example |
||
undefined, | ||
) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why would this type be potentially undefined? Because the machine hasn't initialized yet? If so, could we do something like:
Or whatever the un-initialized value for There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It is ok it uses undefined, it should not happen tho but the useAuth hook is doing the type validation already. I see creating empty context values as an anti pattern. There is a good blog post about this somewhere, I will try to find it. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please do - I wasn't aware and would love to read more. I'm curious how this pattern handles:
For example, if you had an auth context that returned the following values:
It might be nice to not have the entire context return value undefined if There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, at somepoint this provider is going to pass values like these instead of machine actors but I thought it would be too much to do right now. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The undefined is just a type thing tho since the initialization happens when the component is used on AuthContext.Provider and pass the value props. It also help us to throw an erro if the user is using the context or the hook outside of the Provider. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. About errors I don't think we need to be too much specific. We make that in the machines but I don't see too much vale tho and it adds significantly work. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. About the naming, I think I only was able to understand it now 🤦♂️ |
||
|
||
export const AuthProvider: FC<PropsWithChildren> = ({ children }) => { | ||
const authService = useInterpret(authMachine) | ||
|
||
return ( | ||
<AuthProviderContext.Provider value={{ authService }}> | ||
{children} | ||
</AuthProviderContext.Provider> | ||
) | ||
} | ||
|
||
// The returned type is kinda complex to rewrite it | ||
// eslint-disable-next-line @typescript-eslint/explicit-module-boundary-types -- Read above | ||
BrunoQuaresma marked this conversation as resolved.
Show resolved
Hide resolved
|
||
export const useAuth = () => { | ||
BrunoQuaresma marked this conversation as resolved.
Show resolved
Hide resolved
|
||
const context = useContext(AuthProviderContext) | ||
|
||
if (!context) { | ||
throw new Error("useAuth should be used inside of <AuthProvider />") | ||
} | ||
|
||
const auth = useActor(context.authService) | ||
|
||
return auth | ||
} |
Uh oh!
There was an error while loading. Please reload this page.