fix(elements-dev-portal): query invalidation on jwt refresh #2550
Conversation
kaylachun
changed the title
✅ Deploy Preview for stoplight-elements-demo ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for stoplight-elements ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| @@ -8,7 +8,7 @@ import { getBranches } from '../handlers/getBranches'; | |||
| export function useGetBranches({ projectId }: { projectId: string }) { | |||
| const { platformUrl, platformAuthToken } = React.useContext(PlatformContext); | |||
| return useQuery( | |||
| [...devPortalCacheKeys.branchesList(projectId), platformUrl, platformAuthToken], | |||
There was a problem hiding this comment.
is there a user id or some other context we can use?
There was a problem hiding this comment.
or like if the user is actually logged out or not?
There was a problem hiding this comment.
@daniel-white We do have state.auth.isLoggedIn that we can pass through to the provider. Would that work?
There was a problem hiding this comment.
Ok added the isLoggedIn context here 9db422a
There was a problem hiding this comment.
Is that going to be an issue for anonymous users who never log in?
There was a problem hiding this comment.
@brendarearden I just tested it and it works as an anonymous user. My understanding is the array being passed in to useQuery is used as a key and invalidated if any of those values change
kaylachun
changed the title
Elements Default PR Template
In general, make sure you have: (check the boxes to acknowledge you've followed this template)
CONTRIBUTING.mdOther Available PR Templates:
CONTRIBUTING.md