davidbruant / baredux Goto Github PK

https://medium.com/agoric/preventing-reentrancy-attacks-in-smart-contracts-3899bf837f23

 increaseCount2(state){
            return {
                count = state.count + 1
            }
        }

it should be count: state.count + 1, right ?

(based on feedback from @davidbgk )

const store = new Store({
    state: {
        count: 0
    }, 
    mutations: {
        increase(state, supplement){
            state.count += supplement
        }
    }
})

const {state, mutations, subscribe} = store;

console.log(state.count) // 0

mutations.increase(2)

subscribe(state => {
    console.log(state.count) // 2
})

count is 2 right after the call to increase, so the subscribe isn't really useful

container components are components that are arbitrarily deep in the component tree but have a direct access to the store without the store being passed as props (they use a context so any component can access the store and container components transform the store into props with mapStateToProps)

Right now, baredux has no explicit support for container components, but i consider them a meaningful use case

To begin with, let's write an example of what it would take to write a container component with a React Context manually
If that's annoying to do by hand, let's provide a helper in the library

Unless Google Search results quickly change to something about this library, this is going to become embarassing :-/

At least :

• before-mutation: (state, mutationPath, args)
• after-mutation: (state)
• after-microtask-mutations: (state)