Skip to content

Commit 185aa82

Browse files
committed
Whitespaces ✂️
1 parent 3d4754f commit 185aa82

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

activesupport/lib/active_support/backtrace_cleaner.rb

+7-7
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
module ActiveSupport
2-
# Backtraces often include many lines that are not relevant for the context under review. This makes it hard to find the
2+
# Backtraces often include many lines that are not relevant for the context under review. This makes it hard to find the
33
# signal amongst the backtrace noise, and adds debugging time. With a BacktraceCleaner, filters and silencers are used to
44
# remove the noisy lines, so that only the most relevant lines remain.
55
#
66
# Filters are used to modify lines of data, while silencers are used to remove lines entirely. The typical filter use case
7-
# is to remove lengthy path information from the start of each line, and view file paths relevant to the app directory
8-
# instead of the file system root. The typical silencer use case is to exclude the output of a noisy library from the
7+
# is to remove lengthy path information from the start of each line, and view file paths relevant to the app directory
8+
# instead of the file system root. The typical silencer use case is to exclude the output of a noisy library from the
99
# backtrace, so that you can focus on the rest.
1010
#
1111
# ==== Example:
@@ -15,9 +15,9 @@ module ActiveSupport
1515
# bc.add_silencer { |line| line =~ /mongrel|rubygems/ }
1616
# bc.clean(exception.backtrace) # will strip the Rails.root prefix and skip any lines from mongrel or rubygems
1717
#
18-
# To reconfigure an existing BacktraceCleaner (like the default one in Rails) and show as much data as possible, you can
19-
# always call <tt>BacktraceCleaner#remove_silencers!</tt>, which will restore the backtrace to a pristine state. If you
20-
# need to reconfigure an existing BacktraceCleaner so that it does not filter or modify the paths of any lines of the
18+
# To reconfigure an existing BacktraceCleaner (like the default one in Rails) and show as much data as possible, you can
19+
# always call <tt>BacktraceCleaner#remove_silencers!</tt>, which will restore the backtrace to a pristine state. If you
20+
# need to reconfigure an existing BacktraceCleaner so that it does not filter or modify the paths of any lines of the
2121
# backtrace, you can call BacktraceCleaner#remove_filters! These two methods will give you a completely untouched backtrace.
2222
#
2323
# Inspired by the Quiet Backtrace gem by Thoughtbot.
@@ -50,7 +50,7 @@ def add_filter(&block)
5050
@filters << block
5151
end
5252

53-
# Adds a silencer from the block provided. If the silencer returns true for a given line, it will be excluded from
53+
# Adds a silencer from the block provided. If the silencer returns true for a given line, it will be excluded from
5454
# the clean backtrace.
5555
#
5656
# Example:

0 commit comments

Comments
 (0)