title: Laravel: Should I stick with camel case names for Eloquent relationship methods?
body: <p>Laravel encourages us to use snake_case, e.g. first_name, for model attribute names.  In particular, when snake case is used to access an attribute from outside the class, it will automatically look for an accessor named getFirstNameAttribute.</p>
  
  <p>When it comes to model relationships however, it seems more natural to use camel case.  For example, if a stadium has multiple access points, then the <code>stadium</code> class might have an <code>accessPoints()</code> method.  I can call this method as a property (<code>$stadium-&gt;accessPoints</code>) to retrieve a list of access points, or I can call it as a method (<code>$stadium-&gt;accessPoints()</code>) to get an instance of the underlying query builder.</p>
  
  <p>This is different to how I would normally approach naming conventions.  I would normally name attributes using the same case (either snake_case, or camelCase), irrespective of how the attribute is realised.  </p>
  
  <p>I am now embarking on a large Laravel project.  Should I stick with the two different syntaxes, or am I likely to regret it down the track?</p>