fetch and assign async inputs and token details on transaction detail live

[tenmoves]

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes #774

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Tested locally on the page

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[samuelmanzanera]

I think this one is not necessary to use async here as it's a direct read of the ETS table.

[tenmoves]

ok thanks, so I will keep everything inside handle_transaction function, except the 3 fields related to tokens and inputs.
do you think it's useful to first process inputs send a msg and assign and then spawn another task for tokens or it's not worth it ? (I think it's not worth it)

[samuelmanzanera]

I think it might, because the token information is a "good to have" but not a "must to have", whereas the list of inputs is a hard requirement.

[tenmoves]

done

[samuelmanzanera]

Thanks for the PR. Seems ok for me.
Waiting the next with the stream of inputs.