Small notes about those steps:
-
First step is unclear as
employee_idshould have been available before, so no comment. -
Second step has a lot of redundancy. 1) No need to specify
get? trueifget_byis used. 2) No need forargument :tenantas all actions have opts that includetenant. So the same action can be written as:
read :get_by_code do
get_by :code
end
- 3) But even that is not needed as I see that you use code interface to invoke the action. In that case you don’t actually need custom action at all and can use default read (that’s assumes that you have one) with
get_byoption like this:
code_interface do
define :get_by_code, action: :read, get_by: :code
end
- Third is step is okay one. To pass tenant with new step two you would do
tenant: changeset.tenantas the second argument. 1) You haveattribute_writable? trueforemployee_idbut if you did it only forChangeset.change_attributeto work then you can remove the option and useChangeset.force_change_attribute. 2) In my opinion better to renametag_idargument totag_codefor clarity. 3) Based on code it seems like the argument must be present, so good to addallow_nil?: false.






















