u/ItsAllInYourHead

I decided to finally give TanStack Form a try. All of their other libraries by them that I've used have been great, and I've heard nothing but good things about it. And a decent amount of people seem to be using in production.

But I immediately hit what I would think would be a HUGE problem with ANY form library: if you submit your form to your server, and it returns an error - how do you surface that in the form library.

Apparently the answer is: you don't?

There is an onSubmit function you pass to useForm. This is where you make your network request or whatever. But what happens if that fails? There appears to be no way to deal with that! You can manually set errors, apparently, but the form's isSubmitSuccessful property is going to still be true. And the user won't be able to resubmit unless they change a field (so, for example, if the network request fails for an unrelated reason, you can't just resubmit).

It's all very bizarre to me. How is anyone using this in production? I'm just completely baffled by this. Who is realistically using this? And who are these people saying it's ready for production use?

Here's a bunch of issues/discussions around it:

• How to handle server errors?
• Is it possible to receive field errors from onSubmit failure responses?
• onServer errors being cleared very aggressively
• Form cannot be resubmitted after setting onSubmit.form error via setErrorMap unless a field value changes

I've spent a lot of time over the past few weeks looking into various ORMs and SQL Builder options. I'm not happy with any of the ORMs, and I think a SQL Builder would be ideal. But they all seem to be in maintenance mode or not actively developed anymore.

• Squirrel - Hasn't had any updates in 2 years despite 69 open issues and 27 pull requests. The documentation is quite poor, too (though it's quite straight-forward)
• goqu - Hasn't been updated in 3 years, with 116 issues and 28 PRs.
• dbr - No updates in 2 years

Jet is quite popular, but I felt like I was really fighting with the code generation trying to customize it for use with PostGIS.

I know sqlc is very popular, but the lack of support for dynamic queries is problematic.

It seems like every option I look at has fairly significant downsides. I know a lot of people advocate for writing raw SQL, but that is quite error-prone and brittle in my opinion.

Why is the DB landscape for Go so limited, when other languages have much richer, full-featured options (Entity Framework in .Net, ActiveRecord with Ruby/Rails, Hibernate in Java, tons of Node options, etc)?