Igor Gassmann

Results 43 issues of Igor Gassmann

## Problem Currently, we don't properly destroy SQLite databases in OPFS. When deleting a database, we need to remove not just the main database file, but also all associated files:...

enhancement
adapter:web
sqlite

## Problem `AccessHandlePoolVFS` has two methods with overlapping responsibilities for file deletion: - `resetAccessHandle(zName)` in packages/@livestore/sqlite-wasm/src/browser/opfs/AccessHandlePoolVFS.ts:146 - `jDelete(zName, syncDir)` in packages/@livestore/sqlite-wasm/src/browser/opfs/AccessHandlePoolVFS.ts:252 Both methods handle file cleanup but with different interfaces...

adapter:web
refactor
sqlite

## Problem There are two related architectural issues with the current AccessHandlePoolVFS implementation: 1. **Duplicated utilities**: `opfs-sah-pool.ts` contains utilities like `decodeAccessHandlePoolFilename` that re-implement concerns already handled by `AccessHandlePoolVFS`, creating duplication...

adapter:web
refactor
sqlite

## Summary Replace the current `store.subscribe()` change detection mechanism in `ThreadClientDO` with the new `store.events` API once PR #753 is merged. ## Current Implementation ThreadClientDO currently uses `store.subscribe()` to monitor...

enhancement
example
blocked-upstream

## Problem `useQuery()` doesn't currently support React Suspense, which means components must handle loading states manually even when wrapping them in Suspense boundaries. This creates verbose code with null checks...

enhancement
DX
integration:react

## Summary Implement authentication for the email client example app without requiring external OAuth providers (Google, GitHub, etc.). The authentication should work entirely locally without requiring users to set up...

enhancement
example
needs-research

## Summary Implement business rule validation for thread label operations to ensure data consistency and demonstrate proper validation patterns in an event-sourced system. ## Business Rules to Enforce 1. **System...

enhancement
example
event-sourcing

## Problem Currently, LiveStore enforces a strict 1-1 relationship between event logs and state DBs. Each store has exactly one event log and one state DB, and a state DB...

enhancement
design decision
feedback-wanted
needs-research
event-sourcing

## Problem Statement The current architecture of LiveStore powerfully centers the Event as the primary concept. Events are undeniable facts about what has happened and are excellent for building the...

needs-research

This issue has been converted to a project [Enhance OpenTelemetry Observability for Sync Logic](https://linear.app/livestore/project/enhance-opentelemetry-observability-for-sync-logic-17c188cec546) --- ## Summary Improve LiveStore's OpenTelemetry (OTel) observability around sync operations by migrating non-Effect code to...

syncing
otel