Possible name collisions in contract state

[balasan]

If a contract contains any of the following public variables it would create a naming collision in the drizzle store: initialized, 'synced', 'events'

I propose keeping the contract state in inside a separate state object:

• would be nice to add the contract methods in there as well so we don't have to access the drizzle instance to call functions (this is a very confusing and cumbersome experience right now)

contracts: {
    contractName: {
      initialized,
      synced,
      events,
      state: {
        callerFunctionName: {
          argsHash: {
            args,
            value
          }
        }
      },
      methods: {}
    }
  },

[julien51]

Another approach would to be to let allow generateStore to be invoked with other arguments such as some app reducers, initialState and middlewares.

[julien51]

I did this in my own branch:

• passing reducer
• passing default state
• passing middleware

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been closed, but can be re-opened if further comments indicate that the problem persists. Feel free to tag maintainers if there is no reply to further comments.

[cds-amal]

For 2.0 consideration