Included resource choosing wrong Arel table

I'm running into an issue where including one resource (user) ends up using another Arel table (account), and thus the include blows up with Internal Server Error: key not found: 11. 11 is the Account ID of the user, but the user ID is 68, which is specified on the parent resource as user_id.

I've stepped through the code a bit to determine that pluck_attrs in JSONAPI::Resource#preload_include_fragments has the wrong Arel::Table but I'm not sure what the cause of that is.

My models and resources are configured in a very straightforward manner:

JobApplication < ApplicationRecord
  belongs_to :user, inverse_of: :job_applications, touch: true, counter_cache: true
end

User < ApplicationRecord
  has_many :job_applications, inverse_of: :user, dependent: :destroy
end

Any idea why this would be happening?

Commencez dans JSONAPI::Resource#preload_include_fragments et examinez comment pluck_attrs sélectionne son Arel::Table pendant l’include JobApplication/User décrit. Reproduisez le problème avec la configuration de l’association indiquée dans le rapport, puis vérifiez que l’inclusion de user utilise user_id 68 plutôt que Account ID 11 et ne déclenche plus l’erreur indiquant que la clé est introuvable.