Releases: simplybusiness/rabbit_feed
v3.0.3
Bug fix for Unsupported value 7000 days of type ActiveSupport::Duration
error, caused by:
https://github.com/rails/rails/blob/5-1-stable/activesupport/CHANGELOG.md
In #28204 we deprecated implicit conversion of durations to a numeric which represented the number of seconds in the duration because of unwanted side effects with calculations on durations and dates.
v3.0.2
This fixes a bug that was breaking apps when deployed to an environment where rspec is not installed.
The stack trace looked like this:
rabbit_feed-3.0.1/lib/rabbit_feed/testing_support/rspec_matchers/publish_event.rb:1:in `require': cannot load such file -- rspec/expectations (LoadError)
from rabbit_feed-3.0.1/lib/rabbit_feed/testing_support/rspec_matchers/publish_event.rb:1:in `<top (required)>'
from rabbit_feed-3.0.1/lib/rabbit_feed/testing_support.rb:1:in `require'
v3.0.1
Drop support for Airbrake versions < 5.0. Adds support for Airbrake-Ruby.
v3.0.0
- Improved standardisation of code styling with Rubocop
- Tested with latest bunny (2.6.2) and avro (1.8.1) releases
- Removed backwards compatibility with 1.0 schema version
- Cleaned up custom rspec matcher:
- Removed
.with
chain - Removed option to pass a block to the
.publish_event
method - Introduced
.including
chain allowing partial matching on event payloads - Introduced
.asserting
chain allowing custom assertions to be performed - See: https://github.com/simplybusiness/rabbit_feed#rspec
- Removed
Add block support on rspec test matcher
This change will allow you to pass block as follows.
it 'publishes a create event' do
expect{
post :create, beaver: { name: 'beaver' }
}.to publish_event('user_creates_beaver') do |payload|
expect(payload['beaver_name']).to match(/ea/)
end
end
rabbit feed rspec matcher will clear the TestingSupport.published_events
v2.4.2
v2.4.1
v2.4.0
Introduces a command line console that allows the user to print any messages published to the console. See: https://github.com/simplybusiness/rabbit_feed#console-consumer
v2.3.10
Introduce RabbitFeed.configration.consumer_exit_after_fail
which you can set in your rabbit_feed config yaml file.
With this flag on, it will terminate rabbit feed consumer as soon as any error in processing payload.
Default behaviour: consumer_exit_after_fail / off