The Bookkeeping Pattern
Published 📅: ....
Last modified 📝: ....
Share this post on BlueskySee discussion on Bluesky
I've found myself lately working with a decent number of Array.prototype.reduce and useReducer uses. With both of these, I've been reaching for what I'm going to call the "bookkeeping pattern"[1]Jump to footnote.
Before diving into the code, I wanted to step back a bit and outline when and where this pattern could be useful.
Let's start with a simple example, imagine you have an array of strings, that can contain some duplicates, and we want to narrow it down to only an array of unique strings. Sure, I know you could also import {uniq} from 'lodash' and be done with it (or use [...new Set([...array])]), but let's say that we wanted to implement this logic via Array.prototype.reduce for a minute!
In order to remove the duplicates, we need some way to know if we've "seen" a value before, while we could use some external value for that, we could also stash that value within the result of our reducer. Essentially we manage our own bookkeeping within the reduce call!
Let's look at some code:
let fruits = [
'apple',
'banana',
'kiwi',
'strawberry',
'apple'
];
{
// First path, maintaining the bookkeeping separate from the reduce:
let seen = new Set();
let reducedFruits = fruits.reduce((acc, fruit) => {
if (!seen.has(fruit)) {
seen.add(fruit);
acc.push(fruit)
}
return acc;
}, []);
}
// Second path - bake in the bookkeeping
// __within__ the reduce accumulator!
let reducedFruits = fruits.reduce(
(acc, fruit) => {
if (!acc.seen.has(fruit)) {
acc.seen.add(fruit);
acc.fruits.push(fruit);
}
return acc;
},
// Note: Our default accumulator changed shape!
{
fruits: [],
seen: new Set()
}
)
// Note: We need to grab the value we care about from the reduce call
.fruits;Alright, you might be saying that this looks like overkill for this example, clearly that [...new Set(fruits)] would be far easier and I would agree for this use case.
Let's talk about a slightly more difficult use case where I've seen this pattern become really useful: managing incremental form submissions within React with useActionState!
Imagine we have a multi-step form, something like a progressive disclosure experience where you enter your name, then your email, and maybe finally a message for example.
We could manage this form state all client side with useState's or a useReducer, and then perform a manual form submission (either mimicking it with fetch, or calling form.requestSubmit()), but we could also build it in a way that should work without JS as well!
Enter useActionState and Server Actions in React, we can build a multi-step form building on the concept of accumulating some state within our reducer (server action)!
In our case, we can stash the formData value on our state so we can read back from it within components to re-fill the fields in the form after a submission.
You can test this out in this minimal demo app, the source for that app is available in this repo.
The gist boils down to both the server action:
type State = {
status: 'name' | 'email' | 'note' | 'error' | 'complete',
formData: FormData
};
async function incrementalSendAction(
prevState: State,
formData: FormData,
): Promise<State> {
"use server";
switch (prevState.status) {
case "name": {
if (formData.get("back") === "true") {
return { status: "name", formData };
}
return { status: "email", formData };
}
case "email": {
if (formData.get("back") === "true") {
return { status: "name", formData };
}
return { status: "note", formData };
}
case "note": {
if (formData.get("back") === "true") {
return { status: "email", formData };
}
// regular submission after filling out all the fields
// validate the form data
let { name, email, note } = Object.fromEntries(formData.entries());
if (!name || !email || !note) {
return { status: "error", formData };
}
// do something with the form data
// success!
return { status: "complete", formData };
}
default:
return prevState;
}
}and the usage of useActionState:
let [state, action] = useActionState(incrementalSendAction, initialState);From this - we can access the previous submitted formData via state.formData, allowing us to re-fill the inputs with the previous submitted value:
<Input
name="name"
// undefined on first render, filled in after first submission
defaultValue={state.formData.get('name')}
/>Now we get all the benefits:
- Minimal state management
- What state there is, lives on the server
- The form works great with and without JavaScript
- The rendering logic is easy to reason about
The beauty of this also is that it's "Just React"™ and a minimal pattern built on top of the concepts we learned with Array.prototype.reduce!
Footnotes:
👆Back to reference Although I'm sure that there is an existing name for this concept/pattern - if you know what it is called reach out and I'll update my blog post!
Tags:
Bluesky Post and Comments:
Loading comments...
Related Posts
Web Development
Published: ....
Have you ever found the need to change the image you render on a web page based on the current preferred color scheme of your theme?
Published: ....
Have you ever wanted to create a class in JavaScript or TypeScript but also have the initialization be async? Here's a quick tip on a pattern that I've used in the past!
Published: ....
I recently launched a rewrite and redesign of this personal website, I figured I'd talk a bit about the changes and new features that I added along the way!
Published: ....
A quick tip to implementing CSS theming that's compatible with Server Side Rendered applications!
Published: ....
A brief overview on how we launched The Bikeshed Podcast, including a deep dive in our recording and distribution workflows!
Published: ....
A quick tip outlining how to provide specific TypeScript type definitions for a local module!
Published: ....
Some rough thoughts on building a file-system routing based web application
Published: ....
Slicing software: why vertical is better than horizontal.
Published: ....
What if you could author an entire web application in a single file?
Published: ....
A quick way to handle resetting internal state in components when a parent form is submitted!
Published: ....
A brief look at Import Maps and package.json#imports to support isomorphic JavaScript applications!
Published: ....
A collection of tech talks that I regularly re-watch and also recommend to everyone!
Published: ....
Some features and functionality that I'd like within a React Server Component compatible framework.
Published: ....
A (running) collection of Bluesky tips, tools, packages, and other misc things!
Published: ....
A proposal for a minimal variant of TypeScript!
Published: ....
Sharing a few core recommendations when working within monorepos to make your life easier!
Published: ....
This is a quick post noting that Next.js should now work with Deno v2!
Published: ....
React components have a fundamental contract that is often unstated in their implementation, and you should know about it!
Published: ....
Replace that old useState and useEffect combo for a new and better option!
Published: ....
A quick look at the applications and tools that I (generally) use day to day for web development!
Published: ....
There are a variety of different markdown "standards" out there, and sometimes they're not all that consistent
Published: ....
Proposing a solution for sharing core "business" logic across services!
Published: ....
There's a common gotcha when creating Web Request and Response instances with Headers!
Published: ....
Feature toggles are often underused by most software development teams, and yet offer so much value during not only feature development but also refactors
Published: ....
A quick introduction to my new side project, hohoro. An incremental JS/TS library build tool!
Published: ....
Two neat tricks for enhancing your site's favicon!
Published: ....
The various risks and pitfalls of open source software run by corporations.
Published: ....
A monorepo template for managing a library and documentation together.
Published: ....
How we solved an almost show-stopping production bug, and how you can avoid it in your own projects.
Published: ....
A(nother) deep dive into one of my recent side projects; tails - a plain and simple cocktail recipe app.
Published: ....
When did semver major changes become so scary?
Published: ....
Leveraging service monitors properly to improve service observability.
Published: ....
A brief recap of how Wayfair changed it's CSS approach not once but twice in the span of 5 years!
Published: ....
A deep dive into one of my recent side projects; microfibre - a minimal text posting application
Published: ....
Pair programming can be good sometimes - but not all the time
Published: ....
A few thoughts on using Suspense with GraphQL to optimize application data loading
Published: ....
A few thoughts on what to do after you launch a new project
Published: ....
A few quick thoughts on burn out and taking a break
Published: ....
A few thoughts on managing complex UI component state within React
Published: ....
A quick overview of the new lifecycle methods introduced in React 16.3
Published: ....
A few thoughts and patterns for using styled-jsx or other CSS-in-JS solutions
Published: ....
A few thoughts on the redesign of my personal site, adopting Next.js and deploying via Now
Published: ....
A few weird things about JavaScript
Published: ....
Building a calendar web application
Next.js
Published: ....
A quick tip to implementing CSS theming that's compatible with Server Side Rendered applications!
Published: ....
Some rough thoughts on building a file-system routing based web application
Published: ....
This is a quick post noting that Next.js should now work with Deno v2!
Published: ....
Feature toggles are often underused by most software development teams, and yet offer so much value during not only feature development but also refactors
Published: ....
webpack, and tools built on it like Next.js, don't support true dynamic imports, but I found a way to trick the system!
Published: ....
A(nother) deep dive into one of my recent side projects; tails - a plain and simple cocktail recipe app.
Published: ....
A deep dive into one of my recent side projects; microfibre - a minimal text posting application
Published: ....
A few thoughts on the redesign of my personal site, adopting Next.js and deploying via Now
JavaScript
Published: ....
Have you ever wanted to create a class in JavaScript or TypeScript but also have the initialization be async? Here's a quick tip on a pattern that I've used in the past!
Published: ....
A proposal for a minimal variant of TypeScript!
Published: ....
A quick overview of the new lifecycle methods introduced in React 16.3
Published: ....
A few thoughts and patterns for using styled-jsx or other CSS-in-JS solutions
Published: ....
A few weird things about JavaScript
Tip
Published: ....
A quick tip for creating roundup or summary notes based on other notes in Obsidian using the Dataview plugin!
Published: ....
Have you ever found the need to change the image you render on a web page based on the current preferred color scheme of your theme?
Published: ....
Have you ever wanted to create a class in JavaScript or TypeScript but also have the initialization be async? Here's a quick tip on a pattern that I've used in the past!
Published: ....
A quick tip to implementing CSS theming that's compatible with Server Side Rendered applications!
Published: ....
Recently Dropbox announced that it was shutting down the Capture app/service, so I sought out an alternative that provided a similar user experience!
Published: ....
A quick tip outlining how to provide specific TypeScript type definitions for a local module!
Published: ....
A (running) collection of Bluesky tips, tools, packages, and other misc things!
Published: ....
React components have a fundamental contract that is often unstated in their implementation, and you should know about it!
Published: ....
Replace that old useState and useEffect combo for a new and better option!
Published: ....
There's a common gotcha when creating Web Request and Response instances with Headers!
Published: ....
How to easily mass-export your custom slack emoji without API access!
Published: ....
Two neat tricks for enhancing your site's favicon!
Published: ....
Zed language server quick tip; fixing Zed's language server
TypeScript
Published: ....
Have you ever wanted to create a class in JavaScript or TypeScript but also have the initialization be async? Here's a quick tip on a pattern that I've used in the past!
Published: ....
A quick tip outlining how to provide specific TypeScript type definitions for a local module!
Published: ....
A proposal for a minimal variant of TypeScript!
Published: ....
A quick introduction to my new side project, hohoro. An incremental JS/TS library build tool!
