chore: move utils.Chain into chain-helpers package #790
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.
Fixes https://github.com/KILTprotocol/ticket/issues/2869.
We discussed about moving the
chain-helpers
module into theutils
package. but after checking both packages, I found it would be more logic to simply move the chainy stuff of theutils
package under theBlockchain
namespace of thechain-helpers
.The new utility functions to parse blocks and retrieve extrinsics, can be accessed as in the following snippet:
I made the input
api: ApiPromise
optional, so that it would allow people to use the default returned byConfigService.get('api')
if they need, but internally it needs to be retrieved once and passed along.