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

Implementing a button for Presence in the 2de kamer #449

Merged
merged 5 commits into from
Nov 11, 2024

Conversation

lodewiges
Copy link
Contributor

@lodewiges lodewiges commented Oct 27, 2024

@lodewiges lodewiges changed the title intial commitImplementing a button for Presence in the 2de kamer Implementing a button for Presence in the 2de kamer Oct 29, 2024
@lodewiges lodewiges marked this pull request as ready for review October 29, 2024 01:03
Copy link

codecov bot commented Oct 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.92%. Comparing base (c18d2b4) to head (28a9bca).
Report is 5 commits behind head on staging.

Additional details and impacted files
@@           Coverage Diff            @@
##           staging     #449   +/-   ##
========================================
  Coverage    99.92%   99.92%           
========================================
  Files          203      207    +4     
  Lines         2708     2733   +25     
========================================
+ Hits          2706     2731   +25     
  Misses           2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Comment on lines +218 to +219
'before being removed from sofia your credits needs to be zero.
Please ask the board to be removed from sofia.')
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice find

@@ -101,6 +103,7 @@ def create_permissions(permission_map)
'article' => %i[read],
'article_comment' => %i[create read],
'board_room_presence' => %i[read],
'study_room_presence' => %i[read],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not so sure about this one. why do old members need to know this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is the same type of information as board room presence, and oudleden are able to view that so that is why i made this choice, however, I do agree and this is not strictly needed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removing the permission for oudleden to view both would be the most logical thing. in my opinion. How do you think about it?

@DrumsnChocolate
Copy link
Contributor

One more remark: all this backend stuff is veryveryvery similar to board room presence, but that does not imply that we should 'fix' anything about that: this is perfectly fine as is, because it's easy to maintain

@lodewiges
Copy link
Contributor Author

One more remark: all this backend stuff is veryveryvery similar to board room presence, but that does not imply that we should 'fix' anything about that: this is perfectly fine as is, because it's easy to maintain

Yes, this is correct. I used the board room presence feature as the starting point. We will not be adding a component similar to this in the future(I think). Besides this leden and bestuur have different permissions for both buttons so I was unsure how to implement it without making it 2 separated components. and maybe in the future you could add a link to the scheduling document in the drop down or integrate it with our own planning tool.

@lodewiges lodewiges added this pull request to the merge queue Nov 11, 2024
Merged via the queue into staging with commit fbf1070 Nov 11, 2024
5 checks passed
@lodewiges lodewiges deleted the feature/2de-kamer-button branch November 11, 2024 15:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants