-
Notifications
You must be signed in to change notification settings - Fork 80
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
Providing a context provider #101
Comments
why not use scrollView? |
What do you mean? |
i think better is keep rendering view inside mentionView better(avoid memories, better handling). And you can wrap the mentionView by scrollView + give maxheight to it. But for your issues, you can refer to v3 alpha then look how it work |
I mean we can move rendering the whole list out of component and have some kind of context to get the render suggestions. |
Please double check the v3-alpha, he did all your purpose.
|
Nice! I didn’t see that. |
Closing the issue as it seems that v3 resolves the issues described here. |
I think it can be a good idea to provide a context provider in order to move suggestion rendering out of the container itself.
Imagine you are having a comment input and a send button next to it. For example:
The text was updated successfully, but these errors were encountered: