-
Notifications
You must be signed in to change notification settings - Fork 711
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only one ParaId variable in the Parachain Template #6744
base: master
Are you sure you want to change the base?
Conversation
/command prdoc --audience=runtime dev --bump=minor |
/cmd --audience runtime_dev --bump minor |
Command "--audience runtime_dev --bump minor" has started 🚀 See logs here |
Command "--audience runtime_dev --bump minor" has failed ❌! See logs here |
/cmd --audience runtime_dev --bump minor |
Command "--audience runtime_dev --bump minor" has started 🚀 See logs here |
Command "--audience runtime_dev --bump minor" has failed ❌! See logs here |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @iulianbarbu
// You MUST set this to the correct network! | ||
para_id: 1000, | ||
}, | ||
Extensions { relay_chain: "rococo-local".into(), para_id: runtime::PARACHAIN_ID }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: can we do the same thing for rococo-local
?
Many problems can occur when building and testing a Parachain caused by misconfiguring the paraid.
This can happen when there are 3 different places you need to update!
This PR makes it so a SINGLE location is the source of truth for the ParaId.