#747 | decode trx input to show contract function call #759
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for testnet-teloscan ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for dev-mainnet-teloscan ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for teloscan-stage ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
We need the decoded view to allow for copy paste of values, it should all be visible or scrollable, I think you can try to make font smaller or have the input take more than one line.
|
|
I changed the table to show multiline text on value cell. |
|
Copy to clipboard by line:
Fixed mobile design:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #747
Deployment
Description
This PR includes the solution for two of the three views that the new TransactionInputViewer component should offer. The Default view requires a refinement of the algorithms, so it was separated in this issue (#762) and will be scheduled apart.
The two views implemented are:
Test Scenarios
https://deploy-preview-759--dev-mainnet-teloscan.netlify.app/tx/0x3c81e5a0636da5d29f2eed4e0487dca3e6f36fe341821882c7d351f2de1bf48e
https://deploy-preview-759--dev-mainnet-teloscan.netlify.app/tx/0x5abb5f2c39a12ccc0cd96c879d3ccd3d756ce7bfca369d72b655349d57de61a6
