-
Notifications
You must be signed in to change notification settings - Fork 0
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
init react-hooks #1
Conversation
Let's add a README with the following:
I'll push an example below. |
Another potential consideration, if we're releasing the repo as a package - might be better to export hooks, context and lib as a class with arguments for custom RPC providers, proto server, etc - as opposed to exporting those folders raw. TLDR: It allows devs to control the package more easily. Other suggestions:
|
src/index.ts
Outdated
@@ -0,0 +1,3 @@ | |||
export * from './context'; | |||
export * from './hooks'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To support tree shaking (and prevent importing unnecessary hooks) its best to import each hook manually.
src/index.ts
Outdated
@@ -0,0 +1,3 @@ | |||
export * from './context'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed earlier, we should use export default ValoremProvider from "/..."
for devs to config their RPCs, etc
This reverts commit 0ffaba4.
Implements VAL-447
waiting on sdk v0.0.2-alpha.0