hookstate | The simple but very powerful and incredibly fast state management for React that is based on hooks | Frontend Utils library

I am trying to combine providers using Riverpod state management. In this scenario, I am creating a view model which contains a function that retrieves a future from that view model class. When I try to load the country data from the VM, the following error is displayed:

"'package:flutter_hooks/src/framework.dart': Failed assertion: line 489 pos 7: '!_debugIsInitHook': Cannot listen to inherited widgets inside HookState.initState. Use HookState.build instead".

TestScreen code:

I have tried using "papparse" but did not get exact data. What is wrong in my code?

I want using CSV file getting all data by JSON format and set into my hookState.

Code:

I am new to Javascript, I am trying to invoke code on onClick event inside React container component below is my code

In the past I did lots of native mobile development on both Android (Java) and iOS (ObjC and Swift). For my server-connected apps, one issue that I had to handle properly was the callback that was called after the app made an HTTP request. For example, suppose I have a screen (an Activity in Android or a ViewController in iOS), and inside that I make an HTTP request to a REST server, expecting some data in response. Most textbooks (unfortunately) provide examples of the HTTP response calling a callback method within the Activity or ViewController itself. Yes it seems reasonable at first glance but there is a big problem in apps with multiple Activities or ViewControllers - what happens if the user navigates away from the screen after the request but before the response comes back? In this case, the app destroys the memory of the first Activity or ViewController, so when the response comes back, it tries to call a method on freed memory, resulting in a crash.

What we had to instead was to use a persistent singleton object (like a class that extends Application in Android or use the appdelegate in iOS) as the class that implemented the callback functions. Any screen that wanted to get results had to register for those results (using listeners in Android or using notifications in iOS). If the user navigated away from the screen, the screen's appropriate lifecycle methods would unregister the listener/notification handler in the screen so that there would never be a case where a callback method is called on freed memory.

Now I am starting to use both React (in browsers) and React Native (in mobile apps). I am using the Axios module for handling HTTP requests. Once again, all the examples I see show callbacks in the React component itself rather than any kind of pattern where there is some sort of persistent singleton or global object that handles the responses and dispatches them to any screens that are still active on the display.

So I have several questions as follows:

For React (in a browser), is this a concern? Can/should I just provide a callback on the component itself, and the browser will not have a problem if I navigate away from the screen mid-request? I suspect browser code is pretty robust these days so I doubt it would crash the browser but would it cause any issues with the webapp?

What about React Native? Since this is basically built on top of mobile native code, will I run into this memory crashing problem if I put the callback in the component itself?

If this is a problem, is there a good pattern to use for a central global persistent object to handle callbacks and dispatch the results to any registered components?

Note that I won't be using redux in my code - instead I plan to use a simpler framework (hookstate, hookstate.js.org) that lets me keep track of global state and use it inside components when updated. This seems sortof like a callback system for global state but it isn't quite clear to me the best pattern for incorporating HTTP requests through modules like Axios into it.

Suggestions?

i tried that setState files data get by RNFS.readDir

but when i set data, state is initialized.

I can pass data between operation hooks by using the ctx.hookState property. Is there something like that for sharing data between remote and operation hooks?

When I acquired some data in the remote hook, how do I access it in the operation hook?