[DPA-1306]: fix(operator-ui): update to latest #15296
Merged
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
Allow user to manually input ChainId and Account Address when there are no selections available. When creating a chain config in operator ui, if the core node is not configured with APTOS RPC, user wont be able to create a chain config because there are nothing to select from in the ChainId and Account Address field in the chain config popup. This is a new scenario for Keystone where a chain config needs to be created even if there are no existing connection to an RPC. Operator UI PR: smartcontractkit/operator-ui#95 JIRA: https://smartcontract-it.atlassian.net/browse/DPA-1306
archseer
approved these changes
Nov 19, 2024
jkongie
approved these changes
Nov 19, 2024
This was referenced Nov 19, 2024
cedric-cordenier
pushed a commit
that referenced
this pull request
Nov 20, 2024
Allow user to manually input ChainId and Account Address when there are no selections available. When creating a chain config in operator ui, if the core node is not configured with APTOS RPC, user wont be able to create a chain config because there are nothing to select from in the ChainId and Account Address field in the chain config popup. This is a new scenario for Keystone where a chain config needs to be created even if there are no existing connection to an RPC. Operator UI PR: smartcontractkit/operator-ui#95 JIRA: https://smartcontract-it.atlassian.net/browse/DPA-1306
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.
Allow user to manually input ChainId and Account Address when there are no selections available.
When creating a chain config in operator ui, if the core node is not configured with APTOS RPC, user wont be able to create a chain config because there are nothing to select from in the ChainId and Account Address field in the chain config popup.
This is a new scenario for Keystone where a chain config needs to be created even if there are no existing connection to an RPC.
Screen.Recording.2024-11-19.at.4.21.48.pm.mov
Operator UI PR: smartcontractkit/operator-ui#95
JIRA: https://smartcontract-it.atlassian.net/browse/DPA-1306