cerebris/jsonapi-resources

(Sorry if this is better as a github issue) but I am trying to upgrade from 0.9 to 0.10 and the way records are loaded broke my registration process.

Currently, I have a user_resource that overrides "#records" so that only the current user (via auth context) can query the user records

# UserResource.rb
  def self.records(options = {})
    if options.dig(:context, :current_user)
      User.none
    else
      _model_class.where(id: user&.id)
    end
  end

When a resource is created in 0.10, we persist the resource to the db and then try to re-load it by calling UserResource#records. But since this is a registration request and there is no current user, the records returns nothing and thus the json response returns {"data": null}, even though the user was successfully created.

Any ideas how to fix this? For this particular modal, I could look at patching in the current_user to the context, but in general, how would you support a resource the user can only write to, but not (typically) read from? E.g. you create a log record and the api returns a created_at, but the user can't fetch that record again

code flow:
In the processor, we call find_fragments after creating a resource:
https://github.com/cerebris/jsonapi-resources/blob/5517f173a55ba2960c4f0852e8c51f8dd76194cc/lib/jsonapi/processor.rb#L404
find_fragments calls resource.records to reload the model that was created based on the _primary_id
https://github.com/cerebris/jsonapi-resources/blob/5517f173a55ba2960c4f0852e8c51f8dd76194cc/lib/jsonapi/active_relation_resource.rb#L107

1. Am I doing this right?
2. Why do we need to reload the object from the db that was just created?