React Context: (CRUD / REST)-ful Entities

wolverineks profile image Kevin Sullivan ・2 min read


Here's a link to a codesandbox that uses react context to create a (CRUD / REST)-like interface to local entities. (think: index, new, show, edit, update, destroy)


Recently, I've been in a codesandbox.io template kick, making starter templates for various purposes. I've got one for generic react, one for react with react-router. And now, I've got one for a react context.

Meat n' Potatoes

In this template, the context provides a restful-ish interface for a Posts entity.

The context provides a state like this:

interface State {
  posts: { [id: string]: Post };
  ids: Post["id"][];


const ids = usePostIds(); // index-ish
const posts = usePosts(); // index
const post = usePost(123) // show / edit

And behavior like this:

const newPost = useNewPost()          // create
const updatePost = useUpdatePost(123) // update
const deletePost = useDeletePost(123) // destroy


<button onClick={() => newPost({ id: 123, title: "first post" })}>Create</button>
<button onClick={() => updatePost({ ...post, title: "updated: })}>Update</button>
<button onClick={() => deletePost()}>Delete</button>


Well, I haven't put it into anything significant yet, but it seeeeeeems like it makes it simple to add a new entity to keep track of, if you want to treat it in a similar way.

I was able to encapsulate some basic async stuff in the components, and keep all the local state management synchronous.

const savePostToRemoteServer = (post: Post) => {
    return wait(1000)
      .then(() => {
        if (!isMounted()) return
      .finally(() => {
        if (!isMounted()) return

I haven't done any error handling, so who know how that would go. Probably keep it all in the components alongside the async stuff.

It's not super faithful to either CRUD or REST and the naming convention is mixed, so...who knows.


Here's the link to the codesandbox if you want to dive more into it.



Let me know what you all think. Your feedback is very valuable.


markdown guide