Redux Resource
  • Home
  • Introduction
    • Motivation
    • Core Concepts
    • Similar Projects
    • Examples
  • Resources
    • Resource Reducers
    • Resource Objects
    • Meta
    • Lists
    • Modifying Resources
  • Requests
    • Request Objects
    • Keys
    • Names
    • Statuses
    • Request Actions
      • Updating Lists
      • Reading Resources
      • Updating Resources
      • Creating Resources
      • Deleting Resources
  • Other Guides
    • Usage With React
    • Tracking Request Statuses
    • Using Request Statuses
    • Custom Action Types
    • Migration Guides
  • Recipes
    • Forms
    • Canceling Requests
    • Unauthorized Responses
    • User Feedback
    • Related Resources
    • Caching
  • Ecosystem Extras
    • Redux Resource Action Creators
    • Redux Resource XHR
    • Redux Resource Prop Types
    • Redux Resource Plugins
      • HTTP Status Codes
      • Selection
      • Reset
      • Included Resources
  • FAQ
    • General
    • State Tree
    • Actions
    • Lists
  • API Reference
    • resourceReducer
    • getStatus
    • getResources
    • upsertResources
    • setResourceMeta
    • actionTypes
    • requestStatuses
Powered by GitBook
On this page
  • Recommendations
  • Using Resource Slices
  1. Recipes

Forms

PreviousRecipesNextCanceling Requests

Last updated 5 years ago

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:

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 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.

react-redux-form
redux-form
meta