Simplify abstractions in our react app #36

New Issue

2026-03-19T22:33:14Z

talksik commented

2026-03-19 22:33:14 +00:00

(Migrated from github.com)

We currently have lots of spaghetti abstractions. It's unclear which layer does what. There are levels of indirection that just lead to leaky abstractions. So we need a serious refactor.

Some of this is due to building for the platform play instead of having direct hooks, functions, components for streams and stream children. Instead, we are dealing with nested particle paths and much more complexity than necessary, for now.

Remove nested particle frontend components, even though the firestore data layer can be kept more generic.
Use interfaces or types for params instead of order-based params, and de-structure in the callee function
Separate ui based components from logic, and use more prop drilling for more manageable patterns where parent owns functionality

We currently have lots of spaghetti abstractions. It's unclear which layer does what. There are levels of indirection that just lead to leaky abstractions. So we need a serious refactor. Some of this is due to building for the platform play instead of having direct hooks, functions, components for streams and stream children. Instead, we are dealing with nested particle paths and much more complexity than necessary, for now. - [ ] Remove nested particle frontend components, even though the firestore data layer can be kept more generic. - [ ] Use interfaces or types for params instead of order-based params, and de-structure in the callee function - [ ] Separate ui based components from logic, and use more prop drilling for more manageable patterns where parent owns functionality

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: FlowyLabs/llink#36