Franz Liedke 95ea40a7c4 Do not use model classes in the migrations ... The model classes encapsulate knowledge about the database that may change. That knowledge may be table names, or the value of constants (such as `Group::MEMBER_ID` in this case). Models may even disappear after a while due to refactorings. In all these cases, this migration would break. Thus, we use Laravel's query builder features which makes building queries almost as easy as using the model - but correct in all cases. :-)		2016-03-20 22:40:42 +09:00
..
js	Upgrade to flarum-gulp 0.2.0 / Babel 6	2016-03-18 09:32:57 +10:30
less/forum	Update for new extension API; implement l10n	2015-07-22 10:15:08 +09:30
migrations	Do not use model classes in the migrations	2016-03-20 22:40:42 +09:00
scripts	Update for composer branch	2015-10-11 15:30:19 +10:30
src	Applied fixes from StyleCI	2016-02-25 22:51:14 -05:00
.editorconfig	Add phpcs, Travis, clean up editorconfig and eslint	2015-09-04 11:36:43 +09:30
.gitattributes	Add gitattributes	2015-09-17 09:10:10 +09:30
.gitignore	Update for composer branch	2015-10-11 15:30:19 +10:30
.styleci.yml	Add StyleCI config	2016-02-26 14:02:14 +10:30
bootstrap.php	Import admin translations	2015-10-11 22:24:33 +10:30
composer.json	Add Composer branch-alias	2016-01-19 17:18:44 +10:30
LICENSE	Update license year range to 2016	2016-01-25 16:52:32 +01:00