In the rpc-request-builder, there's an issue observed where, upon initially inserting an API key and selecting an endpoint, the functionality works as expected. However, upon refreshing the page, the API key reverts to empty in the input value, and the endpoint reverts to its initial state.
Expected Behavior:
It would be beneficial to maintain the state of the API key and selected endpoint even after a page refresh. This would enhance the user experience by eliminating the need to re-enter information after each refresh.
Steps to Reproduce:
Open the rpc-request-builder.
Input an API key and select an endpoint.
Refresh the page.
Observe that the API key becomes empty, and the endpoint reverts to the initial state.
Issue Description:
In the rpc-request-builder, there's an issue observed where, upon initially inserting an API key and selecting an endpoint, the functionality works as expected. However, upon refreshing the page, the API key reverts to empty in the input value, and the endpoint reverts to its initial state.
Expected Behavior:
It would be beneficial to maintain the state of the API key and selected endpoint even after a page refresh. This would enhance the user experience by eliminating the need to re-enter information after each refresh.
Steps to Reproduce:
Additional Information:
https://github.com/NethermindEth/rpc-request-builder/assets/64387054/aa750204-57bf-4ac9-97c8-ed5a8b745c14
cc : @jelilat