Where communities thrive

Join over 1.5M+ people
Join over 100K+ communities
Free without limits
Create your own community

Explore more communities

ethvtx/general

Home of https://github.com/horyus/ethvtx

People

Repo info

Activity

Iulian Rotaru

@mortimr

From what I understand, the store is only aware of

"txs", "contracts", "blocks", "accounts", "events", "vtxconfig", "vtxevents", "vtxpoll", "vtxcache", "auth", "fuse", "localSettings", "app", "walletApp"

but not of "asyncReducers" in your reducers

Try adding a random key yo your state and see if it gives you the same error for this new key

Andrew Redden

@androolloyd

you were right, thanks for the random support

only noticed it when i tried to type safe my state

Iulian Rotaru

@mortimr

:+1:

One nice tool for this is the & operator on types in Typescript

type AppState = State & CustomState

Andrew Redden

@androolloyd

oh shit

for real?

Iulian Rotaru

@mortimr

That's what I do, I define my custom state and reducers in my app, then "merge" the types before giving it to the store creation, and I export this in all my app

https://github.com/ticket721/web-app/blob/7da1cb8d3e5cdb5dcc0d8829c17d260020b8c4b5/utils/redux/app_state.ts#L171

Andrew Redden

@androolloyd

ah shit that is nice

i like that rather than the mono state im using

Iulian Rotaru

@mortimr

It's a very powerful operator, you can do very cool stuff in React with it

https://github.com/ticket721/web-app/blob/7da1cb8d3e5cdb5dcc0d8829c17d260020b8c4b5/web_components/tx/TxProgress.tsx#L21

Andrew Redden

@androolloyd

Yeah funny enough Ive been doing it with Props

just didnt mentally connect it for state

but it makes total sense

not sure why that association never hit

use it when combining in Stylesheets + theme through material ui

Andrew Redden

@androolloyd

How can I force reset the cache if I have set permenant:true on my contracts

all the listeners and stuff too

if a user were to log out of hte app

but then login with a new user

Iulian Rotaru

@mortimr

This is how I use it:

I set permanent to true for contracts that should be loaded for all users
I load contracts in components that require them, and remove them when the component gets unmounted. So if you have user specific contracts, it’s better if you load/unload them dynamically

(also I’ll investigate the listener issues as I saw that a lot of them are getting created.)

Andrew Redden

@androolloyd

@mortimr good to know thx

Iulian Rotaru

@mortimr

An example of how I usually load them https://github.com/ticket721/web-app/blob/7806d572f21ea571b7088565bcefc1312b65bf74/web_components/event/card/index.tsx#L45

Andrew Redden

@androolloyd

Hey @mortimr any update on the listener issue?

Iulian Rotaru

@mortimr

Hi Andrew, I have a lot of work on my project but I will try to free some time to get back on ethvtx (upgrade dependencies, check this listener issue and add erc20 support)

Andrew Redden

@androolloyd

Thanks for the update. With token support perhaps being able to pass a list of addresses to the vortex to manage balances of vs setting them individually

Iulian Rotaru

@mortimr

I can add do that too :)

add that*

Iulian Rotaru

@mortimr

Hey, gonna probably finish what I had to do this week and start working on ethvtx.

I’m going to look into the listener issue, add erc20 support and add eip712 signatures support.

For the erc20 support, I’m planning on doing helpers for the whole payment process, with live status and dynamic dispatchers that should be called on every step in order to do both transfer and allowance within the same process.

For this I think I will add something like a Payment object with status and a “proceed()” method that will make the user go further in the allowance / transfer steps.

Does this sound good to you @androolloyd ? I think you have more experience at working with erc20 than me so what are the main pain points rn ?

Andrew Redden

@androolloyd

Balances is a huge pain point. We don’t use allowances but I can imagine that being desirable as you described .

Iulian Rotaru

@mortimr

Currently working on the listener issue. Identified the problem from VtxContract from inside the store. I will refactor this into a hook (similar to connect from react-redux) to load instances at this point, and properly give the store at this moment only. The issue is coming from the store behing statically stored in the VtxContract class.

I will keep you updated about this, but this means breaking changes

Andrew Redden

@androolloyd

Ok thanks.

Iulian Rotaru

@mortimr

2.1.1 is out, and a new module has been created => react-ethvtx, that contains the new HOC withContracts to inject VtxContract instances into component props (and store relying on a static store instance)

https://www.npmjs.com/package/ethvtx

https://www.npmjs.com/package/react-ethvtx

and the documentation for the new contract handling is at http://doc.ethvtx.com/docs/react_intro

Iulian Rotaru

@mortimr

and stop relying*

Andrew Redden

@androolloyd

Things feel way faster after the update.

I think the load contracts approach can be generalized a bit more.

Iulian Rotaru

@mortimr

What have you got in mind ?

Kris Urbas

@krzysu

Hi Iulian, I've just found your repo with ethvtx, from reading docs it feels better than drizzle, but I haven't tried it yet. Is this project in active development or at least regularly maintained? Are you using it in your production dapps?

Iulian Rotaru

@mortimr

Hi Kris ! The project is not our top priority as it does most of the things we use it for. It is used in our dapps (beta and soon production). I’m here if you have any questions :)

I will plug dependabot soon to make automatic dependency updates

Kris Urbas

@krzysu

cool, thanks for the answer, I will check it out

Ivan Rojas

@impetus1

Hello, just came across this repo, so is this store similar to the pet shop store?

Iulian Rotaru

@mortimr

Hi @impetus1, If by pet shop store you mean this https://www.trufflesuite.com/tutorials/pet-shop and drizzle, this repo is similar to it in the fact that it uses redux as a state management and redux-saga as an engine to fetch the blockchain. It differs in the manner the refresh is handled, the data is stored etc