-
-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Tracking] Refactors prior to 1.x #660
Comments
@austinm911 there's nothing to fix there. You can choose which API you want to use |
Hey there! First off, this library is awesome 🔥 - thanks for all the hard work on it. Is this ticket intended to be a sort of a Roadmap for important issues to fix before a 1.x release? I was looking around for a roadmap the other day and just found this issue. It would be nice to know what you all are thinking as far as an initial release timeline - if you have any plans. The library feels close to release to me and already seems very usable. I'm considering using it on a project but would like to be sure I'm not misunderstanding the state of the library first 😁. |
@JackRobards as far as I am aware, these denote the only breaking changes left before we 1.0. I'm 80% confident (and growing every day) that we will not have to make any further breaking changes until this occurs. Once these are done, we will go from However, this doesn't mark the only things I want to do prior to 1.x. During RC (or maybe before) I'd like to address:
Once these issues are done, I think we're 1.x ready - pending integration with a production codebase.
|
I'm happy to announce for anyone that's subscribed to this issue that we're officially in Release Candidate mode! If you'd like to track our progress to 1.x, I've made an issue here: #813 |
touchedErrors
(instead, useform.state.isTouched && form.state.meta.errors.map()
)touch
API to something closer todontUpdateMeta
and inverttrue
default tofalse
field.getValue
for public usage (was always intended for internal usage. Usefield.state.value
instead)serverValidate
from@tanstack/form/next
to throw when errors occur #783The text was updated successfully, but these errors were encountered: