|
54 | 54 | {Credo.Check.Consistency.SpaceAroundOperators}, |
55 | 55 | {Credo.Check.Consistency.SpaceInParentheses, false}, |
56 | 56 | {Credo.Check.Consistency.TabsOrSpaces}, |
57 | | - |
58 | | - # For some checks, like AliasUsage, you can only customize the priority |
59 | | - # Priority values are: `low, normal, high, higher` |
60 | | - {Credo.Check.Design.AliasUsage, priority: :low}, |
61 | | - |
62 | | - # For others you can set parameters |
63 | | - |
64 | | - # If you don't want the `setup` and `test` macro calls in ExUnit tests |
65 | | - # or the `schema` macro in Ecto schemas to trigger DuplicatedCode, just |
66 | | - # set the `excluded_macros` parameter to `[:schema, :setup, :test]`. |
67 | 57 | {Credo.Check.Design.DuplicatedCode, excluded_macros: []}, |
68 | | - |
69 | | - # You can also customize the exit_status of each check. |
70 | | - # If you don't want TODO comments to cause `mix credo` to fail, just |
71 | | - # set this value to 0 (zero). |
72 | 58 | {Credo.Check.Design.TagTODO, exit_status: 2}, |
73 | 59 | {Credo.Check.Design.TagFIXME}, |
74 | 60 |
|
|
119 | 105 | {Credo.Check.Warning.UnusedRegexOperation}, |
120 | 106 | {Credo.Check.Warning.UnusedStringOperation}, |
121 | 107 | {Credo.Check.Warning.UnusedTupleOperation}, |
122 | | - |
123 | | - # Custom checks can be created using `mix credo.gen.check`. |
124 | | - # |
125 | 108 | ] |
126 | 109 | } |
127 | 110 | ] |
|
0 commit comments