[FEAT] Step 2: CRDT-ify the Data Model

Open
#87 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
react-native, typescript
Domain
database, mobile

Research direction

This is a sub-issue of the Local-first P2P Sync epic (#5). Start by locating the data models for Peaks, Camps, Categories, Templates, ScheduledBlocks, and WeeklyPlans, then review how their mutations currently update state. Done means each model uses CRDT-compatible structures and each mutation produces a CRDT operation rather than replacing the full state.

Written by the indexing model from the issue text.

Description

enhancement sub-issue

Is your feature request related to a problem? Please describe.

This is a sub-issue for [EPIC] Local-first P2P Sync (Offline & Private)

Describe the solution you'd like

Wrap Peaks, Camps, Categories, Templates, ScheduledBlocks, and WeeklyPlans in CRDT-compatible structures. Each mutation must produce a CRDT operation (not a full state replacement).

Describe alternatives you've considered

N/A

Additional Context

Part of the [EPIC] Local-first P2P Sync (Offline & Private) epic.

Parent Epic: #5

Dominant language
TypeScript
Stars
4
Forks
4
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GiZano/LevelUp

All issues in GiZano/LevelUp

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.