form icon indicating copy to clipboard operation
form copied to clipboard

[Tracking] Refactors prior to 1.x

Open crutchcorn opened this issue 1 year ago • 4 comments

  • [ ] Remove touchedErrors (instead, use form.state.isTouched && form.state.meta.errors.map())
  • [ ] Set touch API to default to true
  • [ ] Rename touch API to something closer to triggerRender (ideas welcomed)
  • [ ] Deprecate (not remove) field.getValue for public usage (was always intended for internal usage. Use field.state.value instead)
  • [ ] https://github.com/TanStack/form/issues/783
  • [ ] https://github.com/TanStack/form/pull/726 (technically a breaking change?)

crutchcorn avatar Mar 27 '24 23:03 crutchcorn

Will you include https://github.com/TanStack/form/discussions/476 as it breaks the ESLint/Biome rule ?

austinm911 avatar Jun 04 '24 00:06 austinm911

@austinm911 there's nothing to fix there. You can choose which API you want to use

crutchcorn avatar Jun 04 '24 01:06 crutchcorn

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 avatar Jun 04 '24 15:06 JackRobards

@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) to v0-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)
  • [ ] https://github.com/TanStack/form/issues/753
  • [x] https://github.com/TanStack/form/issues/746
  • [ ] https://github.com/TanStack/form/issues/747
  • [ ] https://github.com/TanStack/form/issues/748
  • [ ] https://github.com/TanStack/form/pull/724
  • [ ] https://github.com/TanStack/form/pull/656
  • [ ] https://github.com/TanStack/form/issues/503 (might be deferred)
  • [ ] https://github.com/TanStack/form/pull/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.

crutchcorn avatar Jun 27 '24 14:06 crutchcorn

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: https://github.com/TanStack/form/issues/813

crutchcorn avatar Jul 06 '24 07:07 crutchcorn