rspec-interactive 0.9.16 → 0.9.17

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: e1774bb9567af252ba0717b0c72db6bbb417950077bd0dc50e1870e12cd0aa6b
4
- data.tar.gz: 4efc9a9543beadb93a5e0326ad7ce3fb561901e4d6afce11d5cd0b93c9986059
3
+ metadata.gz: 90df3b8868b3a3b9eaf62fa025f6db1d1fb9582d57855a17db5da0ba4e9048a6
4
+ data.tar.gz: 6cf1492492738f361f2c87ed5b1206a291af39bbbd4cd46cee47ea5396ce4fcb
5
5
  SHA512:
6
- metadata.gz: 38d2f3a77c58a9e0c20770a8df3a60bfc70f877bc3a87f567e5eb339a14d3470fc1fbedfbf2aa485b7a48403e30dae4d5735384792a39e883a4b227a881c0c6f
7
- data.tar.gz: 88365c869beb95b44ec073a64b2d8539a7ae36d1d188160eb5e5689e09c7c38b561d4999220ef790b5883ce4f31ac86a7829e789f87b22617d406bdfb4a6b6b4
6
+ metadata.gz: f53d1b9783630382c8addcada1cb1fdfbb119f503b64014a31294f52b4b99c138b0f2b7bef490ae5eaa51b3125e4d1f935b58c09c2571cf9cc3c7aaea1255e14
7
+ data.tar.gz: 4514ef8b3e50d92998a95a83ee605893df84e44a92878b12ceafa74140a4bd5b89434f423b5559dfe457851e6d4d01ab22b8676fecadb0c2804d4595a501ce23
data/Gemfile.lock CHANGED
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- rspec-interactive (0.9.15)
4
+ rspec-interactive (0.9.16)
5
5
  pry
6
6
  rspec-core
7
7
  rspec-teamcity (= 1.0.0)
@@ -13,10 +13,10 @@ GEM
13
13
  diff-lcs (1.4.4)
14
14
  ffi (1.15.5-java)
15
15
  method_source (1.0.0)
16
- pry (0.14.1)
16
+ pry (0.14.2)
17
17
  coderay (~> 1.1)
18
18
  method_source (~> 1.0)
19
- pry (0.14.1-java)
19
+ pry (0.14.2-java)
20
20
  coderay (~> 1.1)
21
21
  method_source (~> 1.0)
22
22
  spoon (~> 0.0)
@@ -2,6 +2,6 @@
2
2
 
3
3
  module RSpec
4
4
  module Interactive
5
- VERSION = "0.9.16"
5
+ VERSION = "0.9.17"
6
6
  end
7
7
  end
@@ -124,13 +124,11 @@ module RSpec
124
124
  end
125
125
 
126
126
  def self.maybe_trap_interrupt
127
- return unless RbConfig::CONFIG['ruby_install_name'] == 'jruby'
128
-
129
- # When on JRuby, Pry traps interrupts and raises an Interrupt exception.
130
- # Unfortunately, raising Interrupt is not enough when RSpec is running since it
131
- # will only cause the current example to fail. We want to kill RSpec entirely
132
- # if it is running so here we disable Pry's handling and rewrite it to include
133
- # special handling for RSpec.
127
+ # Pry traps interrupts and raises an Interrupt exception. Unfortunately, raising
128
+ # Interrupt is not enough when RSpec is running since it may lead to issues when
129
+ # using transactional fixtures. Also, when running in JRuby, it seems to only fail
130
+ # the current example not the entire RSpec run. Here we disable Pry's handling and
131
+ # rewrite it to include special handling for RSpec.
134
132
 
135
133
  Pry.config.should_trap_interrupts = false
136
134
 
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: rspec-interactive
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.9.16
4
+ version: 0.9.17
5
5
  platform: ruby
6
6
  authors:
7
7
  - Nick Dower
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2023-02-01 00:00:00.000000000 Z
11
+ date: 2023-09-28 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: rspec-core
@@ -131,7 +131,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
131
131
  - !ruby/object:Gem::Version
132
132
  version: '0'
133
133
  requirements: []
134
- rubygems_version: 3.2.3
134
+ rubygems_version: 3.3.3
135
135
  signing_key:
136
136
  specification_version: 4
137
137
  summary: An interactive console for running specs.