kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/rubocop/rubocop.rb

27 lines
1.3 KiB
Ruby
Raw Normal View History

[CE] Add Naming/FileName rule checking expected class/module per filename
2018-03-08 07:56:54 -05:00
# rubocop:disable Naming/FileName
Add cop for has_many :through without disabled autoloading Goldiloader is great, but has several issues with has_many :through relations: * https://github.com/salsify/goldiloader/issues/12 * https://github.com/salsify/goldiloader/issues/14 * https://github.com/salsify/goldiloader/issues/18 Rather than try to figure out which applies in each case, we should just do the drudge work of manually disabling autoloading for all relations of this type. We can always use regular preloading for specific cases, but this way we avoid generating invalid queries through Goldiloader's magic.
2018-04-09 07:19:18 -04:00
require_relative 'cop/gitlab/has_many_through_scope'
require_relative 'cop/gitlab/httparty'
Move ModuleWithInstanceVariables to Gitlab namespace And use .rubocop.yml to exclude paths we don't care, rather than using the cop itself to exclude.
2017-11-22 02:50:36 -05:00
require_relative 'cop/gitlab/module_with_instance_variables'
Introduce PredicateMemoization cop and fix offenses with StrongMemoize
2018-01-09 12:30:04 -05:00
require_relative 'cop/gitlab/predicate_memoization'
Use gitlab-styles Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-09-19 11:25:42 -04:00
require_relative 'cop/include_sidekiq_worker'
Adds Rubocop rule for line break around conditionals
2018-01-11 11:34:01 -05:00
require_relative 'cop/line_break_around_conditional_block'
Add cop that checks if add_column_with_default is used with up/down methods
2017-02-08 17:17:15 -05:00
require_relative 'cop/migration/add_column'
Enforce use of add_concurrent_foreign_key This adds a Rubocop rule to enforce the use of add_concurrent_foreign_key instead of the regular add_foreign_key method. This cop has been disabled for existing migrations so we don't need to change those.
2017-02-09 10:52:43 -05:00
require_relative 'cop/migration/add_concurrent_foreign_key'
Add cop to ensure reversibility of add_concurrent_index
2017-03-07 11:08:53 -05:00
require_relative 'cop/migration/add_concurrent_index'
Add a spec for our custom GemFetcher cop
2017-02-08 16:22:36 -05:00
require_relative 'cop/migration/add_index'
Add database helpers 'add_timestamps_with_timezone' and 'timestamps_with_timezone'
2017-06-13 07:44:13 -04:00
require_relative 'cop/migration/add_timestamps'
require_relative 'cop/migration/datetime'
Added cop to blacklist the use of hash indexes These indexes are not recorded in the WAL (at least until PostgreSQL 10) and this isn't worth the minor performance improvement over btree indexes.
2017-07-14 07:19:00 -04:00
require_relative 'cop/migration/hash_index'
Add cop for use of remove_column remove_column should only be used in the up (or change) step of a migration if it's a post-deployment migration. Otherwise there will be downtime due to the ActiveRecord column cache, which we can avoid by using the IgnorableColumn concern in combination with a post-deployment migration.
2017-12-11 11:34:51 -05:00
require_relative 'cop/migration/remove_column'
Add remove_concurrent_index to database helper
2017-04-05 18:53:57 -04:00
require_relative 'cop/migration/remove_concurrent_index'
require_relative 'cop/migration/remove_index'
Rename AddColumnWithDefault to ReversibleAddColumnWithDefault We're going to add another cop that deals with another aspect of `add_column_with_default`, so we need to separate them.
2017-04-24 13:16:33 -04:00
require_relative 'cop/migration/reversible_add_column_with_default'
Add a new RSpec::EnvAssignment cop to prevent assigning to ENV in specs Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-10-11 07:25:40 -04:00
require_relative 'cop/migration/safer_boolean_column'
Add database helpers 'add_timestamps_with_timezone' and 'timestamps_with_timezone'
2017-06-13 07:44:13 -04:00
require_relative 'cop/migration/timestamps'
New Migration/UpdateColumnInBatches cop Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-05-22 12:31:22 -04:00
require_relative 'cop/migration/update_column_in_batches'
Prevent update_column_in_batches on large tables add_column_with_default is implemented in terms of update_column_in_batches, but update_column_in_batches can be used independently. Neither of these should be used on the specified large tables, because they will cause issues on large instances like GitLab.com. This also ignores the cop for all existing migrations, renaming AddColumnWithDefaultToLargeTable where appropriate.
2017-11-17 08:38:14 -05:00
require_relative 'cop/migration/update_large_table'
Use gitlab-styles Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-09-19 11:25:42 -04:00
require_relative 'cop/project_path_helper'
Add a new RSpec::EnvAssignment cop to prevent assigning to ENV in specs Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-10-11 07:25:40 -04:00
require_relative 'cop/rspec/env_assignment'
Introduce a new FactoriesInMigrationSpecs cop Signed-off-by: Rémy Coutable <remy@rymai.me>
2018-03-30 11:18:12 -04:00
require_relative 'cop/rspec/factories_in_migration_specs'
Use gitlab-styles Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-09-19 11:25:42 -04:00
require_relative 'cop/sidekiq_options_queue'
Copy permalink