You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: advanced_usage.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ Packs.create_pack!(
13
13
### Per-file Processors
14
14
Your application may have specific needs when moving files. `Packs` gives a way to inject application-specific behavior into the file move process.
15
15
16
-
You can pass in an array of applicationspecific behavior into the `per_file_processors` parameter of the main method.
16
+
You can pass in an array of application-specific behavior into the `per_file_processors` parameter of the main method.
17
17
18
18
See `rubocop_post_processor.rb` as an example of renaming files in `.rubocop_todo.yml` automatically, which is something you may want to do (as you do not want to fix all style errors when you're just moving a file).
desc'list_top_violations type [ packs/your_pack ]','List the top violations of a specific type for packs/your_pack.'
44
44
long_desc<<~LONG_DESC
45
-
Possible types are: #{POSIBLE_TYPES.join(', ')}.
45
+
Possible types are: #{POSSIBLE_TYPES.join(', ')}.
46
46
47
47
Want to see who is depending on you? Not sure how your pack's code is being used in an unstated way? You can use this command to list the top dependency violations.
0 commit comments