summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #2087 from casperisfine/test-ruby-2.7-preview1copyrightsKyrylo Silin2019-10-231-0/+13
|\ | | | | Test against MRI 2.7.0-preview1
| * Test against MRI 2.7.0-preview1Jean Boussier2019-10-221-0/+13
|/
* Merge pull request #2084 from casperisfine/ruby-27-frozen-stringsKyrylo Silin2019-10-211-1/+1
|\ | | | | Fix Ruby 2.7 compatibility in Pry::Slop#mehtod_missing
| * Fix Ruby 2.7 compatibility in Pry::Slop#mehtod_missingJean Boussier2019-10-011-1/+1
|/
* Merge pull request #2070 from bcgraham/fix-show-negative-rangeKyrylo Silin2019-09-032-2/+9
|\ | | | | Allow negative ranges in hist --show
| * Allow negative ranges in hist --showBrian Graham2019-08-092-2/+9
| | | | | | | | Remove duplicate `opts[:show]` check in hist.
* | Merge pull request #2073 from pry/gemspec-warning-fixesKyrylo Silin2019-08-091-3/+8
|\ \ | | | | | | Gemspec warning fixes
| * | gemspec: fix the 'pessimistic dependency on coderay' warningKyrylo Silin2019-08-091-1/+1
| | |
| * | gemspec: fix the 'identical summary' warning when buildingKyrylo Silin2019-08-091-2/+7
|/ /
* | CHANGELOG: mention #2060Kyrylo Silin2019-08-081-0/+2
|/
* Attempt to allow pasting multiple lines with leading dots (#2060)Josh Cheek2019-07-114-6/+14
| | | | | | Two tests are breaking, and I kind of understand why, but I'm not sure what to do about it. Figured I should commit and send a PR in hopes of another brain being able to help me out :)
* CHANGELOG: mention #2056Kyrylo Silin2019-06-151-0/+4
|
* Merge pull request #2055 from pry/randomize-testsKyrylo Silin2019-06-154-33/+43
|\ | | | | spec_helper: randomize tests
| * spec/commands/show_source: pass binding to pry_eval to fix failuresKyrylo Silin2019-06-151-26/+20
| | | | | | | | | | | | | | There are sporadic failures with some of the tests (seems to be isolated to the code that uses `Pry.config.commands`). Passing `binding` to `pry_eval` seems to be fixing them. To be quite fair, I'm not sure why that happens but it feels like the right fix because we do the same in many other tests.
| * spec_helper: reset Pry defaults after each testKyrylo Silin2019-06-151-0/+1
| | | | | | | | | | | | This is not perfect but this reset `Pry.line_buffer`. `pry_eval` writes to it and makes some tests fail randomly. This should probably be rewritten properly but this hack will do to make the tests pass.
| * spec/code_object: fix broken 'class method lookup' testKyrylo Silin2019-06-151-2/+4
| |
| * spec/editor: make specs order-independent (and sturdier)Kyrylo Silin2019-06-151-5/+16
| |
| * spec_helper: randomize testsKyrylo Silin2019-06-151-0/+2
|/
* Merge pull request #2061 from pry/show-source-doc-examples-refactoringKyrylo Silin2019-06-153-667/+933
|\ | | | | spec/commands/show_{doc,source}: refactor to be order independent
| * spec/commands/show_{doc,source}: refactor to be order independentKyrylo Silin2019-06-153-667/+933
|/ | | | | | | | | | | | A bunch of tests were order-dependent and weren't cleaning up properly after they're executed. This results in complications with #2055 where we want to randomise our test suite. With this change every test defines what it needs and then cleans up properly, instead of relying on the global space and fixtures. P.S. The specs are still quite messy but this change is a step in the right direction.
* Merge pull request #2058 from pry/config-spec-fixKyrylo Silin2019-06-091-2/+6
|\ | | | | spec/config: fix flaky test
| * spec/config: fix flaky testKyrylo Silin2019-06-091-2/+6
|/ | | | | | This spec was failing for me locally (but worked well on Circle). The reason is that `XDG_CONFIG_HOME` is set for me and takes precedence. Therefore, the fix would be to unset it for the test.
* Merge pull request #2057 from pry/env-key-helperKyrylo Silin2019-06-0915-50/+101
|\ | | | | Add Pry::Env and use where it makes sense
| * Use Pry::Env where it makes senseKyrylo Silin2019-06-0912-50/+56
| |
| * Add Pry::EnvKyrylo Silin2019-06-093-0/+45
|/ | | | Env is a helper module to work with environment variables.
* Merge pull request #2056 from aeter/masterKyrylo Silin2019-06-094-13/+31
|\ | | | | Close #2054 - prefer XDG_* paths (if set)
| * Close #2054 - prefer XDG_* paths (if set)A. Nackov2019-06-054-13/+31
|/ | | | | | | | | References #2054 Using XDG_* paths (if set) with preference higher than the home dir, for pry config and history files. Testing: ran `bundle exec rspec`, observed the tests pass.
* MemoizedValue memoizes nil results (#2053)Josh Cheek2019-06-032-4/+18
| | | | I moved the existing `subject` into the test because it didn't make sense for the second test I added.
* Fix tests that fail based on user's environment (#2047)Josh Cheek2019-06-021-10/+18
| | | | | These tests would fail on my machine. I think it is because I have a ~/.pry_history file. I modified them to not depend on the state of my machine.
* Merge pull request #2048 from JoshCheek/fix-test-output-clobbering-itselfKyrylo Silin2019-06-011-1/+1
|\ | | | | REPL prints to the configured output, not directly to $stdout
| * REPL prints to the configured output, not directly to $stdoutJosh Cheek2019-05-291-1/+1
| |
* | Merge pull request #2050 from JoshCheek/remove-rspec-shouldKyrylo Silin2019-06-017-41/+32
|\ \ | | | | | | Remove all remaining `.should`s from the tests
| * | Remove all remaining `.should`s from the testsJosh Cheek2019-05-307-41/+32
| |/
* | Merge pull request #2051 from vaidehijoshi/remove-poemRyan Fitzgerald2019-05-311-10/+0
|\ \ | |/ |/| Remove exclusionary easter egg command
| * Remove exclusionary easter egg commandvaidehijoshi2019-05-311-10/+0
|/ | | | See issue #2049 for more details.
* Merge pull request #2046 from pry/test-suite-silence-warningsKyrylo Silin2019-05-282-1/+4
|\ | | | | spec/pry_defaults: silence unwanted deprecation warnings
| * spec/pry_defaults: silence unwanted deprecation warningstest-suite-silence-warningsKyrylo Silin2019-05-282-1/+4
|/
* Merge pull request #2045 from pry/1991-output-winsize-fixKyrylo Silin2019-05-2614-112/+276
|\ | | | | Merge Pry::Terminal with Pry::Output
| * Merge Pry::Terminal with Pry::OutputKyrylo Silin2019-05-2614-112/+276
|/ | | | | | | | | | | | | | | | | | | | Fixes #1991 (Pry in a non-stdin/stdout PTY uses incorrect window size on non-JRuby platforms) `Pry::Terminal` was built without custom outputs in mind. We would always assume that `$stdout` is what the user wants. This contradicted the `output` config option. Thanks to `Pry::Output`, which we use internally, we can decorate the output that the user passes us with "size" methods. If we do that, we get improved output support for free, so that PTY's `slave` can be passed to Pry and would be able to determine its size correctly (example from #1991). I do suspect that there are still some gotchas. Some commands or portions of code may still be assuming that `$stdout` is the only possible option. This has to be addressed separately, in the scope of https://github.com/pry/pry/issues/1988. The more tests we add, the easier it will be to uncover those spots.
* Merge pull request #2043 from pry/output-refactoringKyrylo Silin2019-05-262-12/+207
|\ | | | | Refactor Pry::Output and add tests
| * Add unit tests for Pry::OutputKyrylo Silin2019-05-261-0/+197
| |
| * output: assign @color inside initializeKyrylo Silin2019-05-261-6/+4
| | | | | | | | Just a shortcut, so we don't expose the whole pry_instance to all of the class.
| * output: rename 'boxed_io' to 'output'Kyrylo Silin2019-05-261-6/+6
|/ | | | | | Surely, `boxed_io` sounds way cooler than plain and boring `output` but I don't think it helps for understanding the code. Although it *is* an IO object, we treat it as output. Hence, it should be output (no boxes involved).
* Merge pull request #2042 from pry/terminal-refactoringKyrylo Silin2019-05-196-13/+13
|\ | | | | terminal: rename 'bang' methods to normal ones
| * terminal: rename 'bang' methods to normal onesKyrylo Silin2019-05-196-13/+13
|/ | | | | | To be perfectly honest, I have no idea why these methods have exclamation marks. Maybe because they may require `io/console`? Even then, there's nothing dangerous in this.
* Merge pull request #2037 from pry/1876-wtf-codeKyrylo Silin2019-05-123-4/+77
|\ | | | | commands/wtf: add the --code flag
| * commands/wtf: add the --code flagKyrylo Silin2019-05-123-4/+77
| | | | | | | | Fixes #1876 (Make `wtf` show code)
* | commands/wtf: fix typo in bannerKyrylo Silin2019-05-111-1/+1
|/
* Merge pull request #2036 from pry/wtf-refactoringKyrylo Silin2019-05-112-50/+176
|\ | | | | Refactoring of 'wtf' and its tests
| * commands/wtf: refactor to avoid duplicationKyrylo Silin2019-05-111-26/+27
| |
View Lorry Controller Status