Open kamescg opened 4 years ago
Patrick note: "similar to containers from back in the early react days"
Cool, just opened a PR that starts with this approach. Returns null by default, only if the consumer provides children will they be returned.
I think I follow where you're going with this.
getters
branch has wip
when the parent has lots of children and wants to know when teh data is avail
if (props.thisCallback) props.thisCallback(value)
Consider investigating https://reactjs.org/docs/hooks-reference.html#usecallback
Create 1 blockchain getter component in
src/components/token
The query needs to read from the ERC20Certificate
getCertificateData
function.Component(s) Logic
ERC20Certificate
contract.ethers-react-system
dispatched read request.@onpaws I want to review this with you, but would be cool to write our smart contract function read components by default not include a render component. The primary responsibility is to handle the request.
Of course you could still pass
children
props if you wanted to render something, but it shouldn't be required and in fact maybe discouraged. It will just be a functional component that only handles this read to on-chain side-effect.