data rendering for qmHash browse has issue while rendering
- Dominant language
- JavaScript
- Stars
- 1.6k
- Forks
- 534
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
When we provide a QmHash on input and clicks on browse button then it resolves the data stored and renders well But if you provide another QmHash and try again then it will still show the old value But it does work if you browse new QmHash after going out of current screen.
Example -
QmHash - QmTev1ZgJkHgFYiCX7MgELEDJuMygPNGcinqBa2RmfnGFu has a string value "Hello, World"
QmHash - QmU15dToS19kmwESk9gk4DJFheayeoQKCmL5pZpue3kTq7 has a string value "Hello, Dev-D"
But when you try to browse each hash screen will always show you the 1st QmHash value which it has rendered.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to ipfs ui app and click on 'Status'
2. Provide the QmHash QmTev1ZgJkHgFYiCX7MgELEDJuMygPNGcinqBa2RmfnGFu in QmHash input section and click the browse button, which will display the result as 'Hello, World'
3. Provide a new QmHash QmU15dToS19kmwESk9gk4DJFheayeoQKCmL5pZpue3kTq7 in QmHash input section and click the browse button, which will again display the result as 'Hello, World' instead of 'Hello, Dev-D'
4. That's the Error
5. Observation, When I perform the same task in 3 steps then it works well
- Input QmHash and press browse, which will show the correct result
- Click on Status again
- Input new QmHash and press browse, which will show the correct result
**Expected behavior**
When we Provide a new QmHash QmU15dToS19kmwESk9gk4DJFheayeoQKCmL5pZpue3kTq7 in QmHash input section and click the browse button, which will again display the result as 'Hello, World' instead of 'Hello, Dev-D'
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- OS: Ubuntu 18
- Browser : NA
- Version [ ipfs-desktop 0.10.2, go-ipfs 0.4.22 ]
**Additional context**
Add any other context about the problem here.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.