Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Add Xcm sender. #2489

Merged
merged 4 commits into from
Mar 1, 2021
Merged

Add Xcm sender. #2489

merged 4 commits into from
Mar 1, 2021

Conversation

shaunxw
Copy link
Contributor

@shaunxw shaunxw commented Feb 22, 2021

Fixes #2405

@shawntabrizi
Copy link
Member

This doesn't look like the right place for this.

You should implement such a thing here: https://github.com/paritytech/polkadot/tree/master/xcm

With a more specific struct name saying how it should be used, and generic usage of the xcm executor.

@shaunxw
Copy link
Contributor Author

shaunxw commented Feb 22, 2021

This doesn't look like the right place for this.

You should implement such a thing here: https://github.com/paritytech/polkadot/tree/master/xcm

I thought this place is only for fundamental XCM definitions that could be used across relay chain and parachain impl.

The XCM sender defined in this PR is only for relay chain's use, as it only do DMP. That's why I put it in common runtime lib. IMHO the relay chain XCM sender might be in a place where less chance developers would use a wrong sender, and I guess this is also the reason the XCM sender which do UMP and HRMP is defined in cumulus, instead of here.

With a more specific struct name saying how it should be used, and generic usage of the xcm executor.

Will update the naming and documentation.

@shawntabrizi shawntabrizi added C1-low PR touches the given topic and has a low impact on builders. B0-silent Changes should not be mentioned in any release notes labels Feb 22, 2021
@shaunxw
Copy link
Contributor Author

shaunxw commented Feb 23, 2021

Another thing I forgot to mention is that this sender depends on dmp and configuration module. It's not possible make it in https://github.com/paritytech/polkadot/tree/master/xcm unless defining traits to abstract dmp and configuration behaviors.

Copy link
Member

@shawntabrizi shawntabrizi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is fine for now then, but long term, I suspect this will be refactored somewhere else.

I don't have a great immediate suggestion.

@bkchr bkchr added A0-please_review Pull request needs code review. and removed D2-breaksapi labels Feb 23, 2021
@shaunxw
Copy link
Contributor Author

shaunxw commented Feb 24, 2021

Looks like this PR needs more approvals as @bkchr added A0-pleasereview label.

Please help to add reviewers. Thanks!

@shaunxw
Copy link
Contributor Author

shaunxw commented Feb 26, 2021

@shawntabrizi @bkchr Could you please help to add reviewers?

@shawntabrizi
Copy link
Member

bot merge

@ghost
Copy link

ghost commented Feb 27, 2021

Missing process info; check that the PR belongs to a project column.

Merge can be attempted if:

  • The PR has approval from two core-devs (or one if the PR is labelled insubstantial).
  • The PR has approval from a member of substrateteamleads.
  • The PR is attached to a project column and has approval from the project owner.

See https://github.com/paritytech/parity-processbot#faq

@bkchr bkchr merged commit 71d46a0 into paritytech:master Mar 1, 2021
@shaunxw shaunxw deleted the sw/add-xcm-sender branch March 1, 2021 20:24
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A0-please_review Pull request needs code review. B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rococo should be able to send XCM
4 participants