Jan Provaznik
0fc9f9d3e7
Add version 4.2 to all existing migrations
...
DB schema generated by a migration may look different in
rails 4 and 5 (because rails 5 may use different default values).
For this reason it's important to explicitly set for which rails
version a migration was written for.
See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912
2018-11-22 13:18:28 +01:00
Sean McGivern
98bb435f42
Enable RuboCop for migrations
...
Migrations shouldn't fail RuboCop checks - especially lint checks, such
as the nested method check. To avoid changing code in existing
migrations, add the magic comment to the top of each of them to skip
that file.
2016-06-09 16:05:25 +01:00
Douwe Maan
503244eb96
Fix specs
2016-03-22 00:23:58 +01:00
Douwe Maan
31266c5be4
Address feedback
2016-03-22 00:09:20 +01:00
Felipe Artur
8d544645f0
Add specs and add visibility level to admin groups
2016-03-21 19:11:24 -03:00
Felipe Artur
bd59e59d01
Add visibility level icon and a couple of specs
2016-03-10 10:38:36 -03:00
Felipe Artur
5551ccd720
Code improvements
2016-03-10 10:38:36 -03:00
Felipe Artur
f2a9ee258e
Add permission level to groups
2016-03-10 10:38:36 -03:00
