Add chain "slug"; use proper chain key for Polygon Amoy (in local configs) #1976
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.
In this PR I eliminate the special case where we'd use
amoy
as a chain key (fake) for what should've beenpolygonAmoy
(the actual chain key for Polygon Amoy testnet).I do so in the following way:
slug
to config extension (topolygonAmoy
's config) – seechains.yml
.getChainKey
to map it to the actual chain key, and inrouteOptions
for proper search query output.This way any chain (new or existing) can have a short preferred identifier to be used in urls. All for the sake of making adding new chains easier.
In addition, the
getPreferredChainName
got renamed togetChainKey
and refactored. It now always returns aChainKey
. It defaults todefaultChainKey
if it fails to identify the candidate, and warns about such situation viaconsole.warn
.