Hey guys, hope you are doing great. I'm Federico, currently working for M-RETS (midwest renewable tracking system) and we are about to deploy a public API. We are using jsonapi-resource for this. We have already implemented the GET methods. Now we are approaching the Create/Updates.
I was wondering if you guys can help me figure things out.
So my first question is, give this code:
def create
@account = Account.new(create_account_params)
@account.organization = current_user.current_organization
@account.status = Account.statuses[:open]
authorize @account, :create?
if @account.save
render json: @account, status: :created, location: @account
else
render_error @account, :unprocessable_entity
end
end
def create_account_params
params.fetch(:data, {})
.fetch(:attributes, {})
.permit(:account_type, :name)
endWhere should I whitelist parameters, where should I add add new data before creating the resource?
JSONAPI::ResourceController.
So I'm not sure where should I implement this part of the code:
@account = Account.new(create_account_params)
@account.organization = current_user.current_organization
@account.status = Account.statuses[:open]It's just basically adding additional data, apart from the request's parameters
Basically, I need to add additional data to the request's parameters, and then create the record.
In this case, as you can see, after creating the request with the user's param, I set the current organization and set the account to active.
In general, where's the place to intercept the request parameters and do something with them? whitelisting, etc?
context see https://jsonapi-resources.com/v0.10/guide/resources.html#Context
after_create callback, https://jsonapi-resources.com/v0.10/guide/resources.html#JSONAPI-Resource-Callbacks, to set the organization from the context which will be on the resource (see the after_save example in https://jsonapi-resources.com/v0.10/guide/resources.html#Context for a similar example.
belongs_to in the following snippet then the test fails. Is that how it is intended?
class Tag < ActiveRecord::Base
belongs_to :taggable, polymorphic: true
belongs_to :post, -> { where(tags: { taggable_type: 'Post' }).eager_load(:posts) }, foreign_key: 'taggable_id'
belongs_to :user, -> { where(tags: { taggable_type: 'User' }).eager_load(:users) }, foreign_key: 'taggable_id'
end.to_sym here, while it is present here. That forces me to use symbols:class Post < ActiveRecord::Base
# ATTENTION: do not use a string here because that confuses
# `JSONAPI::Relationship.polymorphic_types`
# has_many :tags, as: 'taggable'
has_many :tags, as: :taggable
endThird and finally, I was surprised that my script must not assign to variables during database setup:
# ATTENTION: do not assign to `post` because that confuses
# `JSONAPI::Relationship.polymorphic_types`
# post = Post.create! title: 'my first post'
Post.create! title: 'my first post'Those instances ended up in ObjectSpace here and caused troubles.