Skip to content
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

Conversation

luisa-beerboom
Copy link
Member

@luisa-beerboom luisa-beerboom commented Apr 26, 2024

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:

  • Can't see the foreign-meeting submitter names (i.e. missing fields in autoupdate subscriptions or restrictor problems)
  • Origin motion submitter can see forwarded motions in origin meeting's motion list (unlikely)
  • Origin motion submitter appears in participant list of forward meeting (may only happen after opening forwarded motion)

Removed forwarding_user_id relation from the committee, as it loses it's purpose beginning with this PR

Copy link
Member

@r-peschke r-peschke left a 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

@luisa-beerboom
Copy link
Member Author

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.

@luisa-beerboom
Copy link
Member Author

@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.

@r-peschke
Copy link
Member

r-peschke commented Jul 18, 2024

Please fix failing tests. Except this one and the remark from @rrenkert (basing on feature/motion_forward) this is okay for me

@Elblinator Elblinator changed the base branch from feature/motion-forward to main August 1, 2024 10:45
@Elblinator Elblinator changed the base branch from main to feature/motion-forward August 1, 2024 10:47
@Elblinator
Copy link
Member

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

@Elblinator Elblinator enabled auto-merge (squash) August 1, 2024 10:51
@Elblinator Elblinator force-pushed the 2382-enhance-create-forwarded branch from 2140cdd to 78cef3f Compare August 1, 2024 10:56
@Elblinator Elblinator disabled auto-merge August 1, 2024 10:56
@luisa-beerboom luisa-beerboom merged commit 6c5ca92 into OpenSlides:feature/motion-forward Aug 1, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Becquerel projectname feature migration Introduces a new migration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rework behaviour that a User is created if motions are forwarded Enhance motion.create_forwarded
4 participants