fix: explicitly use passed in dest locations for bridgeTransfers #406
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.
Changes
{"parents":"2","interior":{"X1":{"GlobalConsensus":"Polkadot"}}}
) should be intended as Polkadot AssetHub ( e.g.{"parents":"2","interior":{"X2":[{"GlobalConsensus":"Polkadot"},{"Parachain":"1000"}]}}
). Instead relies on the location value passed in{"parents":"2","interior":{"X2":[{"GlobalConsensus":"Polkadot"},{"Parachain":"1000"}]}}
) rather than the relay chains locationSystemToBridge
integration tests to explicitly provideAssetHub
locations for p<>k bridge casesassetHubWETHToRhala
example to atransferAssetsUsingTypeAndThen
call in order to explicitly set AssetHub as the reserve locationparseLocationStrToLocation
util functioncloses: #407