KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
I was reading Uncle Bob book today on Exception handling and what I could recollect from handing null values was that methods should not be handling null values because it clutters the code. I am a little confused with it. I have always thought that a method should always make sure that it's dependencies are not null (unless they are injected in constructor and constructor assures of nullability). For example, if I have a method public void SendMessage(IEmailSender emailSender, contactList list) { if(emailSender == null) { throw new ArgumentNullException("Failed to send message.",MethodBase.GetCurrentMethod().GetParameters[0].Name); } if(list == null) { throw new ArgumentNullException("Failed to send message.",MethodBase.GetCurrentMethod().GetParameters[1].Name); } // rest of code goes here } Am I missing something?
Tags (comma-separated)
Save Edits
Cancel