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
At its core JSONRpcProvider should be a stateless set of functions to make RPC requests. However, in its current form it caches access keys and parses error data immediately.
The access keys management should be handled by a key store, however, until that work is started this functionality will remain here.
As we have found with the runner it is advantageous to return the complete data from the RPC request in a class that provides parsing.
The text was updated successfully, but these errors were encountered:
@willemneal I am sorry . I overlooked about it . I am new to this repo , the issue description is little bit unclear to me . May you explain me what changes/implementation I have to do regarding this issue .
At its core JSONRpcProvider should be a stateless set of functions to make RPC requests. However, in its current form it caches access keys and parses error data immediately.
The access keys management should be handled by a key store, however, until that work is started this functionality will remain here.
As we have found with the runner it is advantageous to return the complete data from the RPC request in a class that provides parsing.
The text was updated successfully, but these errors were encountered: