fix: asset-hub-next specName - #1604
Merged
Merged
Conversation
filvecchiato
approved these changes
Mar 2, 2025
TarikGul
approved these changes
Mar 2, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
Updating the specName for
Asset-Hub-Nextso that it loads the controllers defined in assetHubNextWestendControllers.ts when connected toWestend Asset Hub Nextrather than the default ones.Note
This is no blocker since Sidecar is still working with the
defaultControllerswhich include the essential Staking and Balance endpoints.Testing
Tested with Westend Asset Hub Next endpoint and it is working as expected.