LemmyNet / LemmyNet/jerboa

Saving drafts

Open
#356 7 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

4 - medium/high priority enhancement
Dominant language
Kotlin
Stars
1.3k
Forks
175
Avg merge
6d 22h
Merged PRs (30d)
9

Description

It'd be nice to save drafts so you can finish writing you post afterwards.

Contributor guide

Open the contributing guide

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.

Research direction

The issue does not name any files, tests, or entry points. Start by locating the post-writing flow and existing persistence approach, then define how a draft is saved and resumed; done means an unfinished post can be saved and later continued.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.