# Forms

Redux Resource complements, but does not replace, form libraries. If you're already using a form library, we encourage you to continue using it alongside Redux Resource.

## Recommendations

The following are two popular forms libraries for Redux:

* [react-redux-form](https://github.com/davidkpiano/react-redux-form)
* [redux-form](https://github.com/erikras/redux-form)

Using component state for form data is also worth considering. However you decide to manage your form data, it should work well alongside Redux Resource.

## Using Resource Slices

You can also store form information inside of the resource slice. A Redux best practice is to separate your client-side data from your server-side data, so form information should be kept separate from the actual resource objects themselves.

Instead, you might choose to use [`meta`](/resources/meta.md) for form information, or perhaps an additional "top-level" key within the resource slice, such as `forms`.

One thing to consider before going with this approach is whether or not your form allows a user to modify more than one resource at a time. If it does, then you may want to consider storing the form data outside of an individual resource slice.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://redux-resource.js.org/recipes/forms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.