Restforce v5.0.0 Release Notes
Release Date: 2020-07-10 // almost 4 years ago-
โฌ๏ธ For instructions on upgrading from Restforce 4.x to 5.x, see our "Upgrading from Restforce 4.x to 5.x" guide.
๐ฅ Breaking changes
- ๐ฑ โ ๏ธ Define exception classes for Salesforce errors up-front instead of dynamically at runtime , running the risk that we might miss some errors which should be defined. If any errors are missed, they will be added in patch versions (e.g.
5.0.1
). For more details on this change, see the "Upgrading from Restforce 4.x to 5.x" guide (@presidentbeef, @timrogers). - ๐ฑ โ ๏ธ Deprecate support for Ruby 2.4 , since Ruby 2.4 reached its end-of-life in April 2020 (@timrogers)
- ๐ฑ โ ๏ธ Change the ancestry of
Restforce::UnauthorizedError
so it inherits fromFaraday::ClientError
, notRestforce::Error
. This breaking change was required to expose the response body returned by the API as part of this error - see the non-breaking changes entry below for further details (@michaldbianchi).
Non-breaking changes
- โ Add support for
lostisland/faraday
v1.x, whilst maintaining support for v0.9.x (@ryansch) - โ Add
#empty?
method toRestforce::Collection
, returning whether they are any items in a collection (@bubaflub) - ๐ Allow opting-in to caching on a per-call basis with
Restforce::Client#with_caching
(@swaincreates) - ๐ฆ Expose the response body from Salesforce on
Restforce::UnauthorizedError
andRestforce::NotFoundError
(@michaeldbianchi) - โ Remove the unnecessary depending on the
json
gem, which has been part of the Ruby standard library since v1.9 (@vonTronje)
- ๐ฑ โ ๏ธ Define exception classes for Salesforce errors up-front instead of dynamically at runtime , running the risk that we might miss some errors which should be defined. If any errors are missed, they will be added in patch versions (e.g.