Draft
Conversation
This was
linked to
issues
Oct 30, 2022
Member
|
check out #12 |
1 task
Member
Author
|
@patrickwieth how do we want to proceed with this? Regarding council design and #153. |
Member
|
From the perspective of backend/cardchain the design is fixed and ready to go, yes. |
This file contains hidden or 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
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.
This will add:
Removed the
councilStatusfield and replaced it withcouncilParticipationwhich has astatus, which is analog to oldcouncilStatusand acouncilattribute, which holds the council the user is in.Therefore added the
inCouncilstatus to cards, which is set, when a card is in a council@Niko-Snmyself on the implemnetation in the frontend