Menu

One engine, two render layers: how I built the same data grid for Angular and React
πŸ“°

One engine, two render layers: how I built the same data grid for Angular and React

DEV Community: angularΒ·Muhammet KayaΒ·1 day ago
#aJnibSJl
#devtoangular#devto#dev#framework#engine
Reading 0:00
15s threshold

A data grid is mostly not rendering. Sorting, filtering, grouping, virtualization windows, range

selection, keyboard navigation, clipboard, undo β€” none of it needs a framework. Yet most grids are

written inside one, and the "other framework" version is a wrapper that feels foreign.

I wanted the opposite for OGE UI : one engine with no framework

in it, and a render layer per framework that is native to it. This post is what that looks like in

practice and what it cost.

The split

The engine is plain TypeScript. It owns the data source, the filter and sort pipeline, group

trees, the virtualization math, selection and range state, and the keyboard maps. It knows nothing

about Angular or React and has no runtime dependencies.

The Angular layer exposes that state as signals. Every input, output and piece of grid state is

a signal; there are no decorators and no Zone.js. Components are OnPush and mark exactly what

changed.

The React layer is real components with props, callbacks and controlled state.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.