Repository navigation
[Tracking] Refactors prior to 1.x #660
Description
Activity
- pinned this issue
on Jun 3, 2024 @austinm911 there's nothing to fix there. You can choose which API you want to use
Reacted by Austin and Laurent BlondyHey 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 😁.
Reacted by Zames Chua, CogitoBurrito and Dalibor Homola@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
v0-beta(today) tov0-rc(stable, no breaking changes unless things go really wrong)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:
- Docs for custom components in-app (VIP ticket)
- [FEATURE]: Get SSR working with TanStack Start #753
- [DOCS]: Get the Vue Docs To Be On Par With The React Documentation #746
- [DOCS]: Get the Lit Docs To Be On Par With The React Documentation #747
- [DOCS]: Get the Solidjs Docs To Be On Par With The React Documentation #748
- fix(core): add support to union types for
DeepValue#724 - feat: set field errors from the form validators #656
- Caching Primitives #503 (might be deferred)
- add effect-form-adapter #718 (might be deferred)
Once these issues are done, I think we're 1.x ready - pending integration with a production codebase.
As an aside; I know 1.x has taken a long time to get here. This is because I wanted to wait until we were extremely confident in what we're shipping. I'm very happy with how things are going today, but don't want to ship a v1, then a v2, then a v3 quickly. I want us to stay stable for some time in the future.
Reacted by Jack Robards, Leonardo Montini, Jesse Kelly, Dalibor Homola, Martin and Tobiloba Adedeji 🦀- unpinned this issue
on Jul 6, 2024 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
Reacted by Alex Johnson
touchedErrors(instead, useform.state.isTouched && form.state.meta.errors.map())touchAPI to something closer todontUpdateMetaand inverttruedefault tofalsefield.getValuefor public usage (was always intended for internal usage. Usefield.state.valueinstead)serverValidatefrom@tanstack/form/nextto throw when errors occur #783