Closed jaydonkrooss closed 5 months ago
Works as you described. Just making sure I understand, the goal is that if there is a meeting with no attendees, that it will say somewhere that the meeting is invalid and that it needs to be deleted? I think it may help to make it a little more clear to the user with something a little more eye-catching that the meeting should be deleted if that's the case.
Works as you described. Just making sure I understand, the goal is that if there is a meeting with no attendees, that it will say somewhere that the meeting is invalid and that it needs to be deleted?
Yes, the invalid data should be presented as opposed to crashing the page, which we saw before.
I think it may help to make it a little more clear to the user with something a little more eye-catching that the meeting should be deleted if that's the case.
Good suggestion, I'll look into some error message or at least changing the text inside the table to be more clear.
@jxiao21 I just added a suggestion to delete the meeting in the table entries. This is a rare scenario to begin with so I think that will suffice to indicate to the user that the invalid meeting should be removed.
197 Addresses the issue we've been seeing with meetings without attendees. My solution is to just handle the issue client-side, allowing users to view all affected meetings and manually remove them.
Test plan to replicate local development environment:
delete from officehours_api_attendee where meeting_id={meeting_id}
To test the meeting without attendees in just the Meeting Queue, repeat the above but skip over step 2