-
Notifications
You must be signed in to change notification settings - Fork 744
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
Added tests for XCM barriers: AllowSubscriptions
, WithUniqueTopic
and TrailingSetTopicAsId
#3955
Conversation
… and `TrailingSetTopicAsId`
SetTopic([0; 32]), | ||
]); | ||
|
||
let test_data = vec![ |
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: Not very important, but personally I would find it easier to follow and I think it would also be more extensible if we just asserted each case separately instead of iterating through a vec
. I don't think it would create a lot of duplication.
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.
I saw this pattern on several other places and also used it elsewhere, where I had much more test data (corner) cases than just 4 here :)
As a part of #3692 I will add a new barrier, so I will come back to this and simplify.
… and `TrailingSetTopicAsId` (paritytech#3955) Closes: paritytech#1756
Closes: #1756