Allow user_data to be set during new_user proposal #1488
Merged
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.
Previously users needed to be added by a
"new_user"
proposal, and then could have user data set by"set_user_data"
. This requires finding the assigned user ID (which is hard to do, and should be easier!), and enforces a period of time where the user has no user data.This changes the expected data for
"new_user"
s from just a cert to a fullUserInfo
object, potentially including an initialuser_data
value.