summaryrefslogtreecommitdiff
path: root/Rakefile
Commit message (Collapse)AuthorAgeFilesLines
* rubocop: enable the Style/FrozenStringLiteralComment copKyrylo Silin2019-05-081-0/+2
| | | | This will greatly ease Pry support on Ruby 3.0 (when it's out).
* rubocop: "fix" offences of the Security/Eval copKyrylo Silin2019-03-241-0/+2
|
* rubocop: fix offences of the Metrics/LineLength copKyrylo Silin2019-03-031-2/+6
| | | | | | I realise that some code might be less readable now, but now that we set a good default limit, we protect the codebase from further mess. It's important to do this to prevent adding more mess to already messy code that we have. :doctor:
* rubocop: fix offences of the Style/WordArray copKyrylo Silin2019-03-021-1/+1
|
* rubocop: fix offences of the Style/SpecialGlobalVars copKyrylo Silin2019-03-021-1/+1
|
* rubocop: fix offences of the Style/RescueModifier copKyrylo Silin2019-03-021-1/+5
|
* rubocop: fix offences of the Layout/EmptyLines copKyrylo Silin2018-11-041-1/+0
|
* rubocop: fix offences of the Style/HashSyntax copKyrylo Silin2018-10-131-10/+10
|
* Rakefile: unit test with help of RSpec::Core::RakeTaskKyrylo Silin2018-10-061-25/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | Commit a99861f1b1cea84d044c458ec5fba401d88c6802 broke some tests for me when I try to run them locally. Example failures: ``` Failures: 1) gist nominally logs in Failure/Error: expect(Pad.gist_calls[:login!]).not_to be_nil expected: not nil got: nil 2) show-doc on modules show-doc -a messages relating to -a indicates... Failure/Error: raise CommandError, "No docs found for: #{ obj_name ? obj_name : 'current context' Pry::CommandError: No docs found for: TestClassForShowSource ``` There's little reason to use our own task for specs since RSpec already provides one. Switching to that deletes some old (likely unused) code and fixes the failures for me. Win-win.
* Update Rakefile to properly run specs (#1700)John Mair2017-11-141-1/+1
| | | Use bundle exec
* Explicitly set arch to 'universal' for mingw and mswinDaniel Berger2015-10-131-1/+1
|
* Use CPU-less platforms for windowsEric Hodel2015-04-091-3/+5
| | | | | | | | | | There is no need to include the CPU in the platform string as there is no compiled code shipped in the pry gems. The only difference is the dependency. Pry became a victim of rubygems/rubygems#1058 which will be fixed in rubygems/rubygems#1120. I would also like to raise awareness of proper use of platform parts while I'm fixing the bug in RubyGems.
* Enable warnings during spec runsMatijs van Zuijlen2015-01-231-1/+1
|
* Switch test suite to RSpecJosh Cheek2014-08-101-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Add rake task for running tests on multiple rubiesAndrew Vos2014-07-201-0/+12
|
* Add support for x64-mingw32 platform [Fixes #834]Conrad Irwin2014-05-151-4/+4
|
* Revert "Set architecture to "universal" for Windows (fix #934)"Conrad Irwin2014-05-141-3/+3
| | | | This reverts commit 0ee65eee4e1b452c841a9a94d7c3d6d98a4ebfd6.
* Set architecture to "universal" for Windows (fix #934)universal-architectureRyan Fitzgerald2014-05-021-3/+3
| | | | | | | | | This is based on this commit: https://github.com/djberg96/win32-api/commit/ceb47f0eb48e It should fix the issue where we were only building i386-specific gems for Windows.
* Remove code made obsolete by Bundler dependencyRyan Fitzgerald2014-03-141-13/+0
| | | | | | | Since 2cdf739baa1a7c1a0aa86649c1b0ca902f9f4bad started always loading bundler/setup during tests, we can get rid of some manual load path setup and dependency checking. We should also explicitly add bundler as a development dependency.
* Move Readline-loading specs inside normal suiteRyan Fitzgerald2014-03-131-1/+1
| | | | This simplifies our Rake and Travis config.
* remove 1.8-compatibility hack from Rakefile.Robert Gleeson2014-02-031-9/+0
|
* integration/readline_spec.rb => isolation/readline_spec.rbRobert Gleeson2014-02-031-1/+1
|
* add spec/integration/readline_spec.rbRobert Gleeson2014-02-031-1/+1
|
* dummy commit to force travis to do its thingJohn Mair2013-02-121-1/+1
|
* add a few rake task aliasesJohn Mair2013-02-021-0/+4
|
* All passing arguments to `rake pry`.Conrad Irwin2013-01-271-1/+5
|
* Make the .gemspec canonical instead of generatedRyan Fitzgerald2013-01-011-38/+6
|
* Update baconRyan Fitzgerald2012-12-271-1/+1
|
* Make bacon respect $VERBOSE env var (default=off)☈king2012-12-201-1/+2
|
* Factoring sorted run into 'rake recspec'☈king2012-12-111-4/+22
|
* Use exec to run tests to preserve exit codeConrad Irwin2012-12-091-1/+1
|
* Deduplicate bacon invocation☈king2012-12-091-1/+6
| | | | Surprising how much this thrashed so far.
* Move all fixtures into fixtures/Ryan Fitzgerald2012-12-091-1/+1
|
* Add Mocha for mockingRyan Fitzgerald2012-12-081-1/+2
|
* cleaned up lib/pry/test/helper.rbJohn Mair2012-12-071-1/+1
| | | | | * 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)
* moved test helper.rb to lib/pry/test/helper.rb, so plugins can use our test ↵John Mair2012-11-281-1/+1
| | | | helpers
* Rename for tabcompletion-friendliness.☈king2012-11-151-2/+5
|
* Add simple GuardfileRyan Fitzgerald2012-09-081-1/+2
|
* Add self to author listRyan Fitzgerald2012-09-071-2/+2
|
* Quiet mode for tests againRyan Fitzgerald2012-09-051-1/+1
|
* Temporarily print verbose test outputRyan Fitzgerald2012-09-051-1/+1
|
* Add Bond completion (when available) cirwin++☈king2012-08-181-0/+2
|
* I Young GreedygutsJohn Mair2012-07-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | Cap Of silk moiré, Little wand** Of ivory, Clothes Very dark, Paul watches The cupboard, Sticks out Little tongue At pear, Prepares Gives a poke, And squitters A.R.
* use prompt proc arity instead of to_ary. God this is boringJohn Mair2012-07-131-1/+1
|
* version 0.10.pre.1Conrad Irwin2012-07-051-1/+1
|
* Update to method_source 0.8.pre.2Conrad Irwin2012-06-031-1/+1
|
* Update to slop 3.3.1Conrad Irwin2012-05-311-1/+1
|
* Bump slop dependency to 3.3.0Conrad Irwin2012-05-301-1/+1
|
* Revert "Set Pry::Slop equal to Slop (v2.4.4)"Conrad Irwin2012-05-301-0/+1
| | | | This reverts commit e306ff5584f7ac098fb87167aadd612d161bc74f.
* Set Pry::Slop equal to Slop (v2.4.4)Conrad Irwin2012-05-281-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We've decided not to upgrade our slop dependency to version 3 for several reasons: 1. People who are currently using pry in their programs are using slop version 2; and they may not realise this. Bumping the slop dependency could therefore break people's code in subtle ways. By removing the dependency completely we make it obvious that breakage has occurred, and allows programs to chose their own version of slop. 2. The new version of slop is incompatible with pry. As a command-line tool we use our option parsing library very very intensely; and as such we've grown used to (and even embraced) it's warts, inconcistencies and undocumented behaviours. Upgrading the slop dependency at this point requires a lot of fix up work both on the slop codebase and the pry codebase. 3. The slop API is implicitly part of the pry API for defining custom commands; by changing that API we run a significant risk of breaking people's pry extensions. 4. The problems in 1., 2. and 3. are going to recur every time slop releases a new version. 5. Doing this does not preclude upgrading the version of slop we use in the future. Beacuse 1. will not occur anymore, the only breakage that we can cause is in pry extensions; this seems resonable providing we signal the fact that we're doing it (for example by updating the major version number).
View Lorry Controller Status