support throwing an error on an unsuccessful getParams, getFormData instead of allowing `.data` being undefined

Describe the bug

Often I use getParams like so. I wish getParams just throw an exception on unsuccessful parse instead of me having to check for it everytime

const parsedFormData = await getParams(formData, someSchema)

// I wish I didn't have to do this every time
if (!parsedFormData.data) throw new Error("no data")

// do something with
parsedFormData.data.someField

Your Example Website or App

every app

Steps to Reproduce the Bug or Issue

as listed

Expected behavior

throwing an exception

Screenshots or Videos

No response

Platform

server

Additional context

No response

[kiliman]

We’ve already used getParams for safe parsing. Also, I think that’s the better default. I’m adding the *OrFail() versions. This will be pushed out shortly.

[kiliman]

Closed by 30ab3a1cff39a6d396416a657bb3a0b8c16d7adb