To resolve the above issue, in the DrizzleContract.js file in the Drizzle store, the action type referenced as TransactionsActions.SEND_CONTRACT_TX has been changed toContractActions.SEND_CONTRACT_TX. The action type SEND_CONTRACT_TX can now be accessed there because it is defined as a constant in the file './contracts/constants', which is imported as ContractActions in DrizzleContract.js.
To test that the proposed change fixes the issue:
Run yarn to build (the console output from the compilation should no longer show a warning about this issue)
In the Drizzle Custom Provider example, submit a new stored value, and the value should update correctly
Closes #77
To resolve the above issue, in the DrizzleContract.js file in the Drizzle store, the action type referenced as
TransactionsActions.SEND_CONTRACT_TXhas been changed toContractActions.SEND_CONTRACT_TX. The action typeSEND_CONTRACT_TXcan now be accessed there because it is defined as a constant in the file './contracts/constants', which is imported asContractActionsin DrizzleContract.js.To test that the proposed change fixes the issue:
yarnto build (the console output from the compilation should no longer show a warning about this issue)