Add specName and chainName to Artifacts #69
Merged
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.
specName
comes from an RPC call but AFAICT, nothing returns thechainName
for the registry. Used a switch/case block here but I could see many possible approaches to this:Leave as is. The reason I did this is because TxWrapper's registry will only accept'Polkadot' | 'Kusama' | 'Westend'
, so I explicitly filter for them here.Remove the switch/case and just do thedefault
block now, which capitalizes the first letter ofspecName
. This assumes that all chains and the Polkadot JS API type registry will follow thisspecName
/chainName
pattern.Just removechainName
from the return entirely and let people deal with thisspecName -> chainName
conversion on the outside.chainName
and this is all pointless.To release only after paritytech/txwrapper#161 is in a txwrapper release.