title: Using Route::match() Laravel 5.3
body: <p>Is it unconventional and therefore ill-advised to use the <code>match()</code> method to determine which controller method to use under 1 uniformed named route? I have this code: </p>
  
  <pre><code>Route::match(['get', 'post'], '/add/lecture/{course}', [
      'as' =&gt; 'addLecture',
      'uses' =&gt; Request::isMethod('post') ? 'Main@addLecture':'Main@showAddLecture'
  ]);
  </code></pre>
  
  <p>Which works as expected. But I just want to know if this is a feasible solution, or if I should stop being lazy and create two separate routes (I am not using <code>Route::resource()</code> for a particular reason, so please don't advise me to use that for basic CRUD). I don't mean for this question to be subjective, I presume there is an objective reason as to why this isn't employed very often? </p>