Closed emmabjj closed 1 week ago
There are some codeclimate failures about the ManageEvaluatorsController being too big - too many methods and too many lines. The basic issue is that there is a lot of business logic expressed in the controller. The standard approach to this would be to create a service object that encapsulates this logic and then call into that from the controller. I just watched the youtube video, it's a good overview on the what/why/how. I'm happy to discuss this approach with you when you are ready. Bonus: might be able to refactor that after_create callback into a service too. 🤞
200 - Build Manage Evaluators List
112 - Delete Evaluators
74 - Enter Evaluators
Build the frontend for the manage evaluators list and the functionality. This allows a challenge manager to add an existing evaluator to a specific challenge/phase, invite a new evaluator, delete an evaluator or an invitation, resend an invitation to a pending evaluator, or resend an invitation if the challenge manager tries to add an existing evaluator invitation again.
Added tests to cover changes.
Add/delete/resend functionality
Build Manage Evaluator List, form, and delete modal
Update header and challenge status
WAVE
Form fields are required to add evaluator
Using evaluator_submission_assignments for evaluator submission count
Mobile