feat: co proposer invites frontend implementation #926
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…/user-office-core into SWAP-4336-user-invites
…ation schemas in InviteMutations
…ate authorization logic
…on for invitations
…aphQL mutation definition
…iceProject/user-office-core into SWAP-4368-co-proposer-invites-ui
… async operations
…reate and update methods
added 5 commits
February 11, 2025 16:23
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR builds upon previously implemented backend endpoints and finalizes the feature by
Motivation and Context
As discussed before this feature improves the "add co-proposer" UI window and architecture design wise moves us step closer to remove user data management form the User Office Project
How Has This Been Tested?
Added E2E tests
Fixes Jira Issue
https://jira.esss.lu.se/browse/SWAP-4368
Tests included/Docs Updated?