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
I recently reviewed the list of issues reported for use-funnel and came across a user issue related to hydration problems(#103) when using the App Router.
This appears to be a previously identified problem with an existing solution(#59) however, since it is not documented in the official guide, it may cause confusion for many users.
Possible Solution
I’ve created a draft example of how this issue could be addressed in the documentation.
The wording is subject to change, but I’d like to hear your thoughts on adding this information using the approach shown in the image above.
There are two main reasons for highlighting this issue in that location:
This section is one of the first parts users encounter when searching the documentation to use the library. Placing the information here ensures users are adequately informed about the issue before they begin using the library.
While use-funnel does not provide a separate router specifically for the App Router, it is still compatible with browser history. Including this information explicitly demonstrates that the App Router can indeed be used with the library.
etc.
No response
The text was updated successfully, but these errors were encountered:
Great! This issue was raised a long time ago and is in our backlog. It would be great to be able to use the example you've shown, Thank you for your contributions!
Package Scope
etc
Description
Hello,
I recently reviewed the list of issues reported for
use-funnel
and came across a user issue related to hydration problems(#103) when using theApp Router
.This appears to be a previously identified problem with an existing solution(#59) however, since it is not documented in the official guide, it may cause confusion for many users.
Possible Solution
I’ve created a draft example of how this issue could be addressed in the documentation.
The wording is subject to change, but I’d like to hear your thoughts on adding this information using the approach shown in the image above.
There are two main reasons for highlighting this issue in that location:
This section is one of the first parts users encounter when searching the documentation to use the library. Placing the information here ensures users are adequately informed about the issue before they begin using the library.
While
use-funnel
does not provide a separate router specifically for theApp Router
, it is still compatible withbrowser history
. Including this information explicitly demonstrates that theApp Router
can indeed be used with the library.etc.
No response
The text was updated successfully, but these errors were encountered: