You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe what's incorrect/missing in the documentation
This happens when the React element defined as <Element> in multi line comment sections are not surrounded by backticks. In the screenshot above, the missing element name is <Link> which is here.
Without backticks:
With backticks:
I was going to open a PR for useNavigate but I realised there must be more of these across the codebase. I can probably use a regex (similar to ^\*(.*) <(.*)>) to find all the incorrectly named elements. Looking for feedback on how to go about it. One big PR or multiple small ones and use this as a tracking issue?
Update:
Ended up creating one PR since patch was not that big.
The text was updated successfully, but these errors were encountered:
We just published version 6.17.0-pre.0 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!
Describe what's incorrect/missing in the documentation
This happens when the React element defined as
<Element>
in multi line comment sections are not surrounded by backticks. In the screenshot above, the missing element name is<Link>
which is here.Without backticks:
With backticks:
I was going to open a PR for
useNavigate
but I realised there must be more of these across the codebase. I can probably use a regex (similar to^\*(.*) <(.*)>
) to find all the incorrectly named elements. Looking for feedback on how to go about it. One big PR or multiple small ones and use this as a tracking issue?Update:
Ended up creating one PR since patch was not that big.
The text was updated successfully, but these errors were encountered: