mirror of
https://github.com/pry/pry.git
synced 2022-11-09 12:35:05 -05:00
ebccd57013
John "banister" Mair describes the following key features of commands
as classes:
1. It enables people to extend them by either subclassing or
monkeypatching.
2. It enables them to provide their own API, so that for example, the
Pry::Command::Edit class could have class methods for people to
configure it.
Please, note that I didn't touch easter eggs commands. I also prettified
some strings (your source code reading experience should vastly improve!).
Signed-off-by: Kyrylo Silin <kyrylosilin@gmail.com>
21 lines
561 B
Ruby
21 lines
561 B
Ruby
class Pry
|
|
class Command::Nesting < Pry::ClassCommand
|
|
match 'nesting'
|
|
group 'Navigating Pry'
|
|
description 'Show nesting information.'
|
|
|
|
def process
|
|
output.puts 'Nesting status:'
|
|
output.puts '--'
|
|
_pry_.binding_stack.each_with_index do |obj, level|
|
|
if level == 0
|
|
output.puts "#{level}. #{Pry.view_clip(obj.eval('self'))} (Pry top level)"
|
|
else
|
|
output.puts "#{level}. #{Pry.view_clip(obj.eval('self'))}"
|
|
end
|
|
end
|
|
end
|
|
end
|
|
|
|
Pry::Commands.add_command(Pry::Command::Nesting)
|
|
end
|