-
Notifications
You must be signed in to change notification settings - Fork 10
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
Standup meeting group refactor #138
Conversation
…-learning/PairApp into standup-meeting-group-refactor
joined_card_component.rb co-author: Roc Devenport rubykod@gmail.com
destroy action co-author: Roc Devenport rubykod@gmail.com
joined_card_component.html.erb co-authored-by: Roc Devenport rubykod@gmail.com
controller to render turbo stream on destroy co-authored-by: RocDavenport rubykod@gmail.com
@GALTdea Make sure you fix the CI failures. Looks like something isn't passing lint. |
it would also be helpful if you could add screenshots/flesh out the context for the reviewer, e.g. https://fogel.dev/software/what_makes_a_good_pr/ |
@@ -2,6 +2,7 @@ | |||
|
|||
class FlashComponent < ViewComponent::Base | |||
TYPE_THEMES = { | |||
success: 'success', |
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.
lol, while I generally agree that this should probably be success across the board rather than notice, I'm wondering whether this is the PR to do it or whether we can use the existing notice
Flash and kick updating to success
to another PR?
Thanks for the review Josh! I did see one error that was related to a variable length, I'll try to fix it today! |
Oh that's right, I forgot 😅. Thanks for the review Ariel |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #138 +/- ##
==========================================
+ Coverage 96.57% 97.10% +0.52%
==========================================
Files 119 123 +4
Lines 1488 1518 +30
==========================================
+ Hits 1437 1474 +37
+ Misses 51 44 -7
☔ View full report in Codecov by Sentry. |
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.
Good first attempt! That said, I think there's a bit more work beyond getting the core functionality to work.
app/components/standup_meeting_group/joined_card_component.html.erb
Outdated
Show resolved
Hide resolved
_standup_meeting_group_list_item.erb
display 3 cards per row.
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.
Some comments and nits about the markup and CSS but this is looking like good progress.
Most urgent things:
- A bit worried about the Card container wrapping on mobile. It doesn't at all for me, but judging from your videos, it does for you. I'm definitely interested in getting to the bottom of that. What browser are you using?
- The dynamic buttons on the Cards should definitely be added before merging this imo.
app/components/standup_meeting_group/joinable_item_component.html.erb
Outdated
Show resolved
Hide resolved
app/components/standup_meeting_group/joined_card_component.html.erb
Outdated
Show resolved
Hide resolved
<div class="w-1/2"> | ||
<div class="card-actions flex space-x-2 justify-end"> | ||
<button class="btn btn-sm">Check In</button> | ||
<button class="btn btn-sm">Dismiss</button> |
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.
There are still plans to add the dynamic behavior here, right?
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.
you mean checkin and dismiss? (btw changed the button name to skip). Seems like this could be a different issue, but I'll ask @toyhammered
|
||
respond_to do |format| | ||
format.turbo_stream do | ||
render turbo_stream: turbo_stream.update(helpers.dom_id(@standup_meeting_group, :join_or_leave), component) | ||
flash.now[:notice] = "You have joined #{@standup_meeting_group.name}!" | ||
render 'standup_meeting_groups/joins/create' |
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.
Pretty sure this render
call is unnecessary.
<button class="btn btn-sm">Check In</button> | ||
<button class="btn btn-sm">Dismiss</button> | ||
<br> | ||
<%= link_to 'Leave', standup_meeting_group_join_path(@standup_meeting_group, @standup_meeting_group_user), data: { turbo_method: :delete }, class: 'btn btn-link align-bottom' %> |
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.
It looks like they've pulled leaving off the card in the wireframes. Maybe worth asking Daniel or Ariel about this and if they still want it here.
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.
hmm, yes I see. I'll post a question in discord
app/views/standup_meeting_groups/_standup_meeting_group_list_item.erb
Outdated
Show resolved
Hide resolved
5bfb79e
to
017e16b
Compare
github.com:agency-of-learning/PairApp into standup-meeting-group-refactor
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.
Just a couple of small things to fix and I think it's good to merge. Looks awesome and this code is definitely quite a bit simpler than what was here previously. Awesome work
grid to flexbox
to render JoinableItemComponent
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.
Awesome work!
What's the change?
Notes:
This PR successfully addresses the majority of the specifications outlined in the provided wireframes design. However, we made the decision to split two functionalities into separate issues for better management and clarity.
These two features turned out to be more involved than initially anticipated. Separating them allows us to focus on their implementation more effectively. Also, potential updates outside of this issue might improve how we address them.
Checklist before requesting a review
Screen.Recording.2023-07-25.at.1.02.32.PM.mov
Screen.Recording.2023-07-29.at.12.10.59.PM.mov