Prepare_params vs. transform_params in ash_phoenix?

prepare_params happens just before we handle nested forms, and gets called w/ all top level params, so is the simplest place to modify params.

transform_params is a bit more complex as it allows distinguishing between “is this a nested form” and pattern matching on the form struct who’s params you are modifying.

When in doubt, use prepare_params as a simple callback to modify the params the user submitted before handled by the form.