-
Notifications
You must be signed in to change notification settings - Fork 43
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
use React new Context API #227
Comments
I'm willing to rework the react client for an up-to-date API, with the newer Context API and some custom hooks if you want. Are there any needed features ? I've seen caching in other issues, are there any specifics ? Should a cache invalidation purge everything, or just a path ? |
That would awesome ! |
Is it possible to have a chat about about the react client features ? I have a POC of the react client using hooks, it is quite smaller compared to the current implementation. I would not want to break these features if they are useful for some |
Hi, we could talk about that next week, i'am on holiday right now. |
Hello Julien,
I don't think the array of path is used anymore.
Anyway, something like that would do the job :
const feature1 = useFeature("path1");
const feature2 = useFeature("path2");
...
{ feature1 && feature2 &&
<SomeComponent ... /> }
Regards,
Gauthier
Le mer. 30 déc. 2020 à 18:05, Julien Tanguy <[email protected]> a
écrit :
… Is it possible to have a chat about about the react client features ? I
have a POC of the react client using hooks, it is quite smaller compared to
the current implementation.
However, there are some obscure or undocumented features that I don't
really understand: multiple providers, the possibility to provide an array
of paths in the feature component, etc.
I would not want to break these features if they are useful for some
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#227 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACOLAZRDAUW67CKYL5AMIV3SXNMVXANCNFSM4G2KHLPA>
.
|
Hi, how far did this get? |
I had a POC at some point, but I probably lost it. I remember that the core features were quick to implement. |
No description provided.
The text was updated successfully, but these errors were encountered: