-
Notifications
You must be signed in to change notification settings - Fork 13
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
pallet-fellowship 2 #203
pallet-fellowship 2 #203
Conversation
btw This isnt put into the runtime yet, just the pallet has been made. |
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.
Looks good
} | ||
Ok(()) | ||
} | ||
fn ensure_role_in( |
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.
cant we use one function
seems both are similar except one checks a vec?
Are you concerned about the potential compute/block time?
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.
The idea behind this was so we can just use an ensure_role_in
instead of doing multiple ensure_role
As for compute time i guess its the developers responsibility to ensure the input isn't from the user and isn't over bounds.
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.
Got it, thanks. LGTM!
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.
Looks really good, we can deploy to rococo to test
Superseding #179
Ripping the fellowship pallet into its own branch as a couple features that are on the main fellowship branch were there for testing.
Issue: #151