* add Pry::Testable, and friends.
This commit replaces lib/pry/test/helper.rb by using category modules.
There's now:
* Pry::Testable:
* Pry::Testable::Evalable
* Pry::Testable::Mockable
* Pry::Testable::Utility
* Pry::Testable::PryTester
'include Pry::Testable' includes all of the above.
For the pry test suite it worked out best to include 'Pry::Testable' at the top-level.
In plugins I've written though this hasn't been the case, and I only normally need:
Pry::Testable::Evalable. So it reduces pollution for the third-party cases, which this
code is intended for since it lives within lib/ of the project.
What do you think?
* breaking change: add set_testenv_variables and unset_testenv_variables
* breaking change: add Pry::Testable::Variables, and rename
constant_scope() to temporary_constants().
* breaking change: rename inject_var as insert_variable, and move its
definition to Pry::Testable::Variables.
* include Pry::Testable::Evalable & include Pry::Testable::Variables into
the top-level, but keep the other two modules spec-local.
* document third argument of insert_variable.
* update CHANGELOG.md
* note changelog entry is a breaking change
* update documentation
Fixes#651 ({after,before}_command hooks should be unified with
Pry::Hooks system)
* The support for the `Pry.commands.{after,before}_command` API was kept
* Hooks defined via the older API use random names
* The order of hooks execution was changed from LIFO to FIFO
Removes Bacon and Mocha
Reasoning explained in this comment: https://github.com/pry/pry/issues/277#issuecomment-51708712
Mostly this went smoothly. There were a few errors that I fixed along
the way, e.g. tests that were failing but for various reasons still
passed. Should have documented them, but didn't think about it until
very near the end. But generaly, I remember 2 reasons this would happen:
`lambda { raise "omg" }.should.raise(RuntimeError, /not-omg/)` will pass
because the second argument is ignored by Bacon. And `1.should == 2`
will return false instead of raising an error when it is not in an it
block (e.g. if stuck in a describe block, that would just return false)
The only one that I felt unsure about was spec/helpers/table_spec.rb
`Pry::Helpers.tablify_or_one_line('head', %w(ing)).should == 'head: ing'`
This is wrong, but was not failing because it was in a describe block
instead of an it block. In reality, it returns `"head: ing\n"`,
I updated the test to reflect this, though I don't know for sure
this is the right thing to do
This will fail on master until https://github.com/pry/pry/pull/1281 is merged.
This makes https://github.com/pry/pry/pull/1278 unnecessary.
* use a plain old Slop instance instead of `Options`;
* remove `ClassCommand::Options` and its tests;
* add clearer subcommand example (for `Command#subcommand` method);
* refactor `ClassCommand#slop`;
* refactor `ClassCommand#complete`.
Slop v3.4.0 has introduced full-featured subcommands. There is no need
in Pry specific code anymore.
When you create a class command, there is a problem with `:listing`
option, which doesn't carry the correct default value. Consider the
example:
class MakeMeHappy < Pry::ClassCommand
match 'woot'
end
`MakeMeHappy` command matches against 'woot' String, but its `:listing`
option is set to the "nil" String, which is incorrect. We can fix it by
setting `:listing` explicitly:
command_options :listing => 'woot'
It's a repetitive task, so we can automate it. Holy smoke, this why we
all use computers, after all!
With help of this commit there is no need to set `:listing` manually.
Pry will handle it for you.
Signed-off-by: Kyrylo Silin <kyrylosilin@gmail.com>
* removed most historicla junk from lib/pry/test/helper.rb
* relocated recalcitrant junk to the local spec/helper.rb (this isn't exposed to 3rd parties)
A few things were missing. I had to add a new method and slightly adjust
ClassCommand#slop method. Without these changes subcommands doesn't work
properly.
Add some unit tests for subcommands.
Signed-off-by: Kyrylo Silin <kyrylosilin@gmail.com>
Create `ClassCommand::Options` class, which ties up sub commands and
default options together.
Let's consider the command `food make --tea`. `food` is a command,
`make` is a sub command and `--tea` is an option of `make` sub command.
We can access `--tea` via `opts[:make][:tea].
Also, we can check the freshness of our food like so: `food --freshness`.
`--freshness` is a default option. We can access it like so:
`opts.freshness?` or `opts[:freshness]`.
Add unit tests for `ClassCommand::Option` and some other tests that
reflect the additions.
Finally, document everything and fix different typos in the existing
documentation.
Signed-off-by: Kyrylo Silin <kyrylosilin@gmail.com>
