v1.7.6

1.7.6 (2024-11-06)

Bug Fixes

• Gem version check (#483) (68e2492)

v1.7.5

1.7.5 (2024-09-16)

Bug Fixes

• Fixes error in version check for ActiveRecord adapter introduced in #478 (#479) (42c82c3)

v1.7.4

1.7.4 (2024-09-11)

Bug Fixes

• update ActiveRecord adapter w/ support for Rails 7.2+ (#478) (8313e33)

v1.7.3

1.7.3 (2024-06-26)

Bug Fixes

• require OpenStruct explicitly (#475) (e0fa18a)

v1.7.2

1.7.2 (2024-06-11)

Bug Fixes

• require necessary ActiveSupport parts in proper order (bb2a488)

v1.7.1

1.7.1 (2024-04-18)

Bug Fixes

• properly display .find vs .all in debugger statements (d2a7a03)
• rescue error from sideloads updated_at calculation, defaulting to the current time (661e3b5)

v1.7.0

1.7.0 (2024-03-27)

Features

• Add support for caching renders in Graphiti, and better support using etags and stale? in the controller (#424) (8bae50a)

Read the PR for more detail, but in short, start using stale? in your controllers, as etag and updated_at, cache_key, and cache_key_with_version methods have been added to the resource.

class EmployeesController < ApplicationController
  def index
   @employees = Employees.all(params)
   respond_with @employees if stale?(@employees) 
  end
end

Also you can now cache the rendering of a graphiti resource.

Graphiti.configure do |c|
  c.cache_rendering = Rails.env.production?
  # c.debug = true
  # with debug enabled extra information about caching will be output
end

Graphiti.cache = ::Rails.cache # or whatever cache you want to use that conforms to the same typical cache interface with .read, .write. fetch, etc.

class EmployeesController < ApplicationResource
  cache_resource, expires_in: 1.week 
end

With the above the actual json-rendering will be cached, often improving response time dramatically. (All render cache keys are namespaced and start with graphiti:render/, in case you're digging in your cache and wanting to see what's what)

v1.6.4

1.6.4 (2024-03-27)

v1.6.3

1.6.3 (2024-03-26)

Bug Fixes

• Remove thread pool executor logic until we get a better handle on what's causing thread pool hangs. refs #469 (7941b6f), closes #471 #470

v1.6.2

1.6.2 (2024-03-22)

Bug Fixes

• thread pool scope and mutex need to be global across all instances of Scope for it to be a global thread pool (#471) (51fb51c)