-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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(core): export useInvalidateAuthStore hook #6405
Merged
BatuhanW
merged 3 commits into
refinedev:releases/november
from
sumeet-y:export-invalidateauth-hook
Oct 30, 2024
Merged
feat(core): export useInvalidateAuthStore hook #6405
BatuhanW
merged 3 commits into
refinedev:releases/november
from
sumeet-y:export-invalidateauth-hook
Oct 30, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 0ec9ce0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
alicanerdurmaz
approved these changes
Oct 30, 2024
aliemir
changed the title
feat: export useInvalidateAuthStore hook
feat(core): export useInvalidateAuthStore hook
Oct 30, 2024
Merged
BatuhanW
pushed a commit
that referenced
this pull request
Nov 7, 2024
- chore(chakra-ui): fix broken tsdoc links #6429 - feat: export useInvalidateAuthStore hook #6405 Resolves #6341 - feat(core): add `<MetaContext />` #6435 - chore(antd): update @ant-design/icons and @ant-design/pro-layout dependencies #6369 Resolves #6363, #5931 - feat(core,antd,mui,mantine,chakra-ui): add new prop to auth-page to p… #6432 Resolves #6431 - fix(core): link component overrides to instead of go #6462 Resolves #6461 - fix(react-hook-form): onChange handler autoSave check in useForm #6459 Resolves #6458 - fix(core): link component ref type is too restrictive (#6464) Resolves #6463
Merged
BatuhanW
added a commit
that referenced
this pull request
Nov 7, 2024
- chore(chakra-ui): fix broken tsdoc links #6429 - feat: export useInvalidateAuthStore hook #6405 Resolves #6341 - feat(core): add `<MetaContext />` #6435 - chore(antd): update @ant-design/icons and @ant-design/pro-layout dependencies #6369 Resolves #6363, #5931 - feat(core,antd,mui,mantine,chakra-ui): add new prop to auth-page to p… #6432 Resolves #6431 - fix(core): link component overrides to instead of go #6462 Resolves #6461 - fix(react-hook-form): onChange handler autoSave check in useForm #6459 Resolves #6458 - fix(core): link component ref type is too restrictive (#6464) Resolves #6463
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
Bugs / Features
What is the current behavior?
useInvalidateAuthStore hook is not exported from auth hooks
What is the new behavior?
exported useInvalidateAuthStore from auth hooks
fixes (#6341)
Notes for reviewers
Do I have to update any docs or write any tests for this PR ?