charpeni/charpeni.com

📝 My personal website and blog.

Hi there 👋

I'm mainly playing with React Native, React, GraphQL, and various Continuous Integrations. I'm an open-source enthusiast (of course!), and I enjoy removing friction from the developer experience. I often describe myself as someone doing the "backend" work of the frontend: frontend architecture and infrastructure. ⚙️ Probably working on the next tool or library to improve your day-to-day.

📝 Latest Blog Posts

• Apollo Client's Hidden Gems: Interface-Based Type Policies
• UI Flickering With Apollo Client: Previous Data to the Rescue!
• GraphQL Enums Are Unsafe
• Open-Ended Unions and Autocomplete With TypeScript
• Testing TypeScript Types: Part 2

🔎 You can also find me on:
Twitter | LinkedIn | Personal Website

charpeni.com's Issues

GroupBy article: "Chaining pure functions" example produces different output

This relates to posts/array-prototype-group-by-to-the-rescue.mdx. Nice succinct article! This issue doesn't really detract from the value of the article, but I thought I'd mention it in case it confuses anyone else.

The "Chaining pure functions" example produces an array of objects, with each object containing a single key (the type). It's also somewhat indirect in converting back and forth from arrays to objects unnecessarily.

In short, I think you could replace:

Object.values({
  ...Array.from(new Set(items.map(({ type }) => type))),
}).map((type) => ({ [type]: items.filter((item) => item.type === type) }));

with:

Object.fromEntries(
  Array.from(new Set(items.map(({ type }) => type)))
    .map((type) => [type, items.filter((item) => item.type === type)])
)

to produce the same output as the .groupBy proposal and other examples.