Skip to content
Snippets Groups Projects
  1. Jul 13, 2015
  2. Jul 10, 2015
  3. Jul 09, 2015
  4. Jul 04, 2015
  5. Jun 26, 2015
  6. Jun 24, 2015
  7. Jun 15, 2015
  8. Jun 14, 2015
  9. Jun 11, 2015
  10. Jun 10, 2015
  11. Jun 09, 2015
  12. Jun 08, 2015
  13. Jun 05, 2015
    • xamgore's avatar
      Code refactoring · 898c14e6
      xamgore authored
      1. Discipline models have the direct access to fields, for example: $discipline->subjectName, so you don't have to remember them (press ctrl+space). Improves static code analysis. Also, if you make a mismatch, ErrorException will be thrown — this is the most important improvement.
      
      2. There are some operations on disciplines (attach new teacher, transfer discipline to another teacher, an so on), so you can use them: $discipline->attachTeacher(53).
      
      3. Discipline model has array access operators, so you must not convert instances with toArray() method. A common way is:
      
      /* PHP */
      $d = Model_Discipline::load($id);
      $d['extraField'] = 127;
      $twig->Discipline = $d;  // is ok, cause $d is like an array
      
      /* Twig */
      {{ Discipline.extraField }}   // call $d->offsetGet('extraField') method
      
      4. Models Faculty, Student, Teachers and Groups have `getDisciplines()` method, and an array of Model_Discipline will be returned.
      
      5. We use camelCase for all fields: in twig, on the PHP level and also in the database.
      898c14e6
  14. Jun 04, 2015
  15. Jun 03, 2015