…ses the partial name correctly. Added an html view for the emails being sent to users when added to teams. Added functionality such that mentored teams users get emails when added to teams. Lastly, added functionality such that the mentor gets a separate email letting them know they are mentoring a team now (there was already working functionality letting users know when a mentor is added to their team).

…displayed correctly.

…entors to be emailed when added to groups. Implemented new way for mentors to be emailed. Added html files for mentor added to group emails. Added an if statement to check whether a user is a mentor or not so they get the right email. Yes I would not do I type check if I didn't have to. However, since mentors are not of a different class than users, I can't actually use polymorphism to fix this issue unless I add an entire new mentor class to the system, which would be far out of the scope of this project.

…l when nil assignment ids were sent to add teams, and another random error where "participants" are sent as a user to add_teams. Apparently this is used for some other feature on Expertiza, but I'm not sure what. As it's outside the scope of this project I just added a type check so that "participants" aren't sent the email other users are. Also added tests for the new mailing functions.

…s to mentored teams. Tested that the code still works as intended.

…ler.rb class instead. Also renamed the function. Changed the implementation on the add_member function to call the new function. Also removed my email that got pushed by accident.

… the topic

…on. Added comments to the "can_add_member" variable in the mentored team decorator. Simplified some code in the add_member function.

… add_member new mailer code. Also added a comment explaining the problem with sending the mail to a user classified as a Participant.

…ck participant. Fixed an error in the add_member function test.