Skip to content

Commit

Permalink
chore: Update TODOs
Browse files Browse the repository at this point in the history
  • Loading branch information
ITenthusiasm committed Apr 12, 2024
1 parent f1b9270 commit 823a231
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 5 deletions.
4 changes: 0 additions & 4 deletions TODO.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,5 @@
# TODO

## Priority

- [ ] Support some kind of `renderByDefault` option

## Documentation

- [ ] Add more detailed examples of how to use `Zod` with the `defaultErrors.validate` option.
Expand Down
4 changes: 3 additions & 1 deletion docs/form-validity-observer/guides.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,9 @@ Here you'll find helpful tips on how to use the `FormValidityObserver` effective
<!--
TODO: Some `Guides` that could be helpful:
1) MAYBE something on how to work with accessible error messages? (Should we also mention `aria-errormessage` vs. `aria-describedby` too? As well as the lack of support for `aria-errormessage`? Or does that belong somewhere else in the docs?)
1) Using `renderByDefault` to render errors to stateful objects (instead of rendering to the DOM).
2) Reconciling error messages sent by the server on the client side.
3) MAYBE something on how to work with accessible error messages? (Should we also mention `aria-errormessage` vs. `aria-describedby` too? As well as the lack of support for `aria-errormessage`? Or does that belong somewhere else in the docs?)
-->

## Enabling Accessible Error Messages during Form Submissions
Expand Down

0 comments on commit 823a231

Please sign in to comment.