Custom reset password form has no validation when submitting

Interesting . I don’t think you’ll want to use that context thing, thats kind of a hack (and likely would have no effect in this case). When you say it doesn’t work do you mean the validation is not applied? Can you show the output of Ash.Resource.Info.action(User, :request_password_reset_with_password)?

That would be:

 %Ash.Resource.Actions.Read{
  arguments: [
    %Ash.Resource.Actions.Argument{
      allow_nil?: false,
      type: Ash.Type.CiString,
      name: :email,
      default: nil,
      private?: false,
      sensitive?: false,
      description: "The proposed identity to send reset instructions to.",
      constraints: [casing: nil, allow_empty?: false, trim?: true]
    }
  ],
  description: "Send password reset instructions to a user if they exist.",
  filter: nil,
  get_by: [],
  get?: false,
  manual: nil,
  metadata: [],
  modify_query: nil,
  name: :request_password_reset_with_password,
  pagination: false,
  preparations: [
    %Ash.Resource.Preparation{
      preparation: {AshAuthentication.Strategy.Password.RequestPasswordResetPreparation,
       []}
    }
  ],
  primary?: false,
  touches_resources: [],
  timeout: nil,
  transaction?: false,
  type: :read
}

Ah, okay, right. So, unfortunately, validations don’t work on read actions. I’ve been meaning to add a compatibility layer for this to allow validations to support queries in addition to change sets (essentially operating only on arguments). In the meantime, what you will need to do to work around this is add a preparation.

preparations do
  prepare ValidateEmail, where: [action_is(:request_password_reset_with_password)]
end

That ValidateEmail would be a standard hand-written preparation.

This is a pretty clear thing we can improve in the framework, and I hope to address this soon to make it a better experience.