As pointed out by @SafaAlfulaij, the new validatorFor functions have not been automatically shared between record sources and their caches. Furthermore they were not shared between memory sources and their forks (generated via fork()). Therefore, validations may have inadvertently been happening at one layer but not the other. This PR resolves this by always passing validatorFor settings along unless an alternative was explicitly provided.
Thanks again for bringing this to my attention @SafaAlfulaij!
As pointed out by @SafaAlfulaij, the new
validatorFor
functions have not been automatically shared between record sources and their caches. Furthermore they were not shared between memory sources and their forks (generated viafork()
). Therefore, validations may have inadvertently been happening at one layer but not the other. This PR resolves this by always passingvalidatorFor
settings along unless an alternative was explicitly provided.Thanks again for bringing this to my attention @SafaAlfulaij!