[FEAT] Step 1: Journal Data Model & Storage

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
54/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
react-native, typescript
Domain
database, mobile

Research direction

Start by reading the parent epic, #4, and locating the app's existing data models and database setup. Define the requested JournalEntry fields and persist entries with expo-sqlite, supporting full-text search. Done means journal entries can be stored and searched with the requested data.

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] Analog-to-Digital Journal

Describe the solution you'd like

Define JournalEntry type (id, date, photos, rawOcrText, editedText, tags, mood). Store in expo-sqlite for full-text search.

Describe alternatives you've considered

N/A

Additional Context

Part of the [EPIC] Analog-to-Digital Journal epic.

Parent Epic: #4

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.