-
-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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: export type NavLinkRenderProps #11553
Conversation
🦋 Changeset detectedLatest commit: 1d3b97a The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
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 |
Hi @zeromask1337, Welcome, and thank you for contributing to React Router! Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once. You may review the CLA and sign it by adding your name to contributors.yml. Once the CLA is signed, the If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at [email protected]. Thanks! - The Remix team |
Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳 |
Thank you for the PR! Would you mind adding a changeset? |
9c2e181
to
ce04f74
Compare
@brophdawg11 have I done it right? |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
Documentation tells us we can use callbacks to utilize various NavLink states
But then restricts us by not letting use type annotation for it
You might say that we can just map over array of links, as usual, but that again restricts us from building more complex and type safe logic