docs: updated usage instructions for type imports #2635
Conversation
This file contains hidden or 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
aks30498
force-pushed
the
pr/documentation-update-for-type-import
branch
from
f781ec0 to
4172dfb
Compare
aks30498
force-pushed
the
pr/documentation-update-for-type-import
branch
from
4172dfb to
8cade38
Compare
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.
Description
This PR updates the
Usage.mddocumentation to clarify the correct way for TypeScript users to import the types directly fromreact-use/lib/[hook], not from the mainreact-useentry point.This change aims to prevent confusion and improve the experience for TypeScript developers using
react-use.Fixes the confusion around type usage as explained in: #2632
Type of change