-
Notifications
You must be signed in to change notification settings - Fork 26
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
New flags in motion.create_forwarded #2399
New flags in motion.create_forwarded #2399
Conversation
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.
Please resolve the remaining conversations
Then please reply to it. Usually, if I reply without changing the code, it is because I want further explanation. |
@r-peschke I've pretty much removed all of the locks on the datastore calls in the forwarding methods, as none of the data called is actually overwritten, since this is, in fact, a type of create function. |
Please fix failing tests. Except this one and the remark from @rrenkert (basing on feature/motion_forward) this is okay for me |
I'll dismiss @r-peschke CR adn merge this pr given that this PR stops work on the issue #2519 @r-peschke comment "this is okay for me" and that the feature is merged into it's own feature branch |
2140cdd
to
78cef3f
Compare
…382-enhance-create-forwarded
6c5ca92
into
OpenSlides:feature/motion-forward
Closes #2382
Closes #2419
For now I handled the problem of "how to use original submitters if they aren't in the target meeting" by using the meeting_user in the other meeting (discussed this with @rrenkert)
If we're going to do this, we should see if there's strange bugs in the client.
Things like:
Removed
forwarding_user_id
relation from the committee, as it loses it's purpose beginning with this PR