my_resource.data raises Graphiti::Errors::RecordNotFound in #create action after Graphiti::Resource#build(params) when the table is empty about graphiti HOT 5 OPEN

Additionally is my_resource.data always nil after Graphiti::Resource#build.
Of course in the case I set raise_on_missing: false here

from graphiti.

@dima4p , from our experience I can tell that it's not a good way to rely on resource.data when the model is not yet saved. If you need to check authorization on the model instance creation step, there is a separate gem for it (assuming you are using ActionPolicy).

from graphiti.

@dima4p , from our experience I can tell that it's not a good way to rely on resource.data when the model is not yet saved. If you need to check authorization on the model instance creation step, there is a separate gem for it (assuming you are using ActionPolicy).

We are using Pundit. I think, that it is important to have the ability to use Graphiti::Resource#build#data to use the new model for authorization.
Now I have to keep in controller the method "#{singular_table_name}_params" and create an additional instance of Model with #new in order to be able to authorize it.

from graphiti.

@dima4p , if you are using Graphiti under the hood, you can hook into model creation via the before_save callback where you will have full access to the newly-built (but not yet saved) model

from graphiti.

@dima4p , one more thing: keep in mind that with JSON:API you have the ability to sidepost multiple resources in one request and thus you will have to either parse the whole resource tree yourself or rely on Graphiti with the approach I mentioned above

from graphiti.