Releases: local-ch/lhs
v26.2.0
What's Changed
- Fix some typos by @abuechler in #414
- Fix expand of data for collections. by @dimameshcharakou in #415
New Contributors
- @abuechler made their first contribution in #414
Full Changelog: v26.1.0...v26.2.0
Contributors
Assets 2
v26.1.0
What's Changed
- Add possibility to override HTTP request's method when chaining save with options. by @dimameshcharakou in #413
Full Changelog: v26.0.1...v26.1.0
Contributors
Assets 2
v26.0.1
Allows to use auth options which takes precedence over auto auth.
https://github.com/local-ch/lhs#automatic-authentication-oauth
Record.options(auth: {bearer: 'ACCESS_TOKEN'}).find(12345)v26.0.0
v25.2.0
v25.1.0
v25.0.4
When performing includes via multiple levels, .e.g.
User.includes(places: :contracts)LHS had problems to continue including nested includes, when there were unexpanded links in between, like places in this example, as users/id/places returns just a list of unexpanded place links.
This PR makes sure that LHS expands loaded links before continuing with includes.
v25.0.3
This fixes an edge case where we include via 2 levels and the second level is missing.
NoMethodError:
undefined method `deep_merge' for nil:NilClass
# ./lib/lhs/concerns/record/request.rb:32:in `block in deep_merge_with_option_blocks'
# ./lib/lhs/concerns/record/request.rb:32:in `map'
# ./lib/lhs/concerns/record/request.rb:32:in `deep_merge_with_op
v25.0.2
some applications were showing weird behavior when using concerns for lhs records.
e.g. causing
TypeError:
superclass mismatch for class Place
Turns out that was because autoloading was autoloading those concerns, even though they are not lhs's business. ruby/rails takes care of autoloading them when loading the original records.
This PR fixes that issue. Unfortunately there was no way of adding a test for that (i've tried) but that issue has been described also by Dima here: #397