feat: NanoContractTransactions component [11]

[alexruzenhack]

Acceptance Criteria

• Should add NanoContractDetailsScreen: it renders details components of a selected Nano Contract
• Should add NanoContractDetails component: it manages details components and some call to actions
  • Should provide action that navigates a user to the explorer
  • Should provide action to unregister the Nano Contract
  • Should provide action to change Nano Contract's address registered
• Should add NanoContractDetailsHeader component: it renders some Nano Contract information
• Should add NanoContractTransactionsListItem: it renders a transaction's summary for each item in a list the Nano Contract's transactions
• Should add UnregisterNanoContractModal component
• Should add SelectAddressModal component
• Should add FeedbackContent component
• Should remove NoNanoContract component once we already have a generalized component FeedbackContent
• Should add registeredNanoContractsIter to MemoryStore
• Should add getRegisteredNanoContracts helper to retrieve the list of registered Nano Contracts
• Should add action NANOCONTRACT_HISTORY_LOADING to assist the history loading process, and add reducer to handle the event
• Should add action NANOCONTRACT_INIT and add init effect on sagas/nanoContract
• Should refactor components to improve its usability and readability
• Should add feedback content to SelectAddressModal

Nano Contract Details Screen

nc-transactions-recording.mp4

Nano Contract Details loading history

Nano Contract Details after error on transactions history load

Select Address Loading

Select Address Loading Error

Note

It depends on:

• feat: nano contract list component [7] #435
• feat: add icons for nano contract transactions [8] #455
• feat: add components for nano contract transactions [9] #456
• feat: add unregister nano contract saga effect [10] #457

Security Checklist

• Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.

[andreabadesso]

Why is this a "mixin"?

[alexruzenhack]

Because there is a pattern for the sagas, they are being used in cycles and major features that also have cycles. This one doesn't belong to a cycle nor to a major feature. Therefore I created this space for standalone effects. It should aggregate future standalone effects as well.

[andreabadesso]

I understand that most of the sagas in src/sagas/wallet.js are related to the wallet load/update "cycle", but not all of them are, like the onResetWallet

IMHO all sagas that are related to the wallet should be in src/sagas/wallet.js, just like all sagas related to "tokens" are in src/sagas/tokens.js

We can discuss having a different structure, like having sagas especifically for those "cycles", but I don't think it should be done in this PR

[andreabadesso]

I understand that most of the sagas in src/sagas/wallet.js are related to the wallet load/update "cycle", but not all of them are, like the onResetWallet

IMHO all sagas that are related to the wallet should be in src/sagas/wallet.js, just like all sagas related to "tokens" are in src/sagas/tokens.js

We can discuss having a different structure, like having sagas especifically for those "cycles", but I don't think it should be done in this PR