lemmy-ui
lemmy-ui copied to clipboard
LemmyNet
Add ability to save draft
In post, comment, and PM.
Required changes to he back-end: https://github.com/LemmyNet/lemmy/issues/3072
Would be handy to be able to save unfinished messages. They should show up in the personal profile (hidden from others), and in the comments tree, drafts may be either loaded automatically or at least a "load draft" button should show up below the respective post/comment.
A way to accomplish about the same is to edit in a separate browser tab, of course. Yet, save draft would add more creative functionality, like being able to save frequently used text blocks, or simply changing to a different device. ... Even collaborative draft editing could be a not far-off thing ...
edit: As a kind-of-trivial addition to this, we could have the ability to clone saved/received messages into a draft ("edit as new message"), which would enable forwarding of messages and posts, and indeed a rudimentary form of collaborative editing as imagined above. :-)
Depending on where you plan on storing the draft, I think this is a backend-related enhancement.
- (lemmy-UI) Storing it in the browser using cookies or local storage. This would be device dependent
- (lemmy) Storing it with the instance, shared across devices.
Personally, I think the latter is preferred, as finishing a thought on the phone, if you had to leave your computer, can be useful.
Depending on where you plan on storing the draft, I think this is a backend-related enhancement.
Yep, I'm aware of that. Wasn't entirely certain (and still have to get used to github customs), where to put it. Figured that people who aren't github regulars or even developers themselves might search for this on the "UX" site rather than the "core" site. It would require changes in both components, anyway. So how is this to be done, have a dev move the request over, or open another appropriate and related request on /lemmy/?
- Storing it with the instance, shared across devices.
Definitely this way.
I'd probably wait till one of the official maintainers react to this issue. You could also create an issue on the backend repo immediately and just leave this one, till someone reacts to it.
Either way, you'd have to create a separate issue, as it isn't possible to move an issue. EDIT: Apparently, it is indeed possible to move an issue
I guess I'm close enough to a maintainer. This will definitely require a change on the backed, but it will also require a change in the UI. No need to close this issue, but you should also open an issue for the backend repo.
