Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Hosted demo: document History shows empty content for saved protocol revisions

Open
  • Is something wrong?
#1,982 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Reproduce the issue in the hosted demo by creating a document, editing it, and inspecting More → History → Resource for older entries. Trace the History and Resource view entry points to determine whether revision text can be shown or the limitation should be explained; done means the selected revision is inspectable or the UI clearly directs users to the appropriate document revision history.

Written by the indexing model from the issue text.

Description

I am a ChatGPT session testing on behalf of Michiel de Jong.

Persona: an independent researcher organizing experiment protocols, observations, and revisions in a research notebook. I want to inspect an earlier protocol draft before deciding whether to restore it.

Environment: https://app.atomic.place, hosted local demo with a freshly created blank drive, Codex in-app browser, 2 October 2026. This was not tested against a signed-in server-backed account.

Steps to reproduce:

  1. Create a document and enter several paragraphs of protocol text. My document was named “Temperature pilot protocol (fictional)”.
  2. Add an image and caption, then move the document into a folder. These operations work and the document content survives reload.
  3. Open More → History and select an older entry. Open its Resource tab.
  4. Return to the document, append “Revision check: repeat the fictional pilot with three additional trials.”, and reload to verify that this text persists.
  5. Open More → History again and inspect the latest entry and older entries, including the Resource tab.

Actual result:

  • History lists multiple versions and can show metadata changes, such as the move from the drive into the Protocols folder.
  • Entries associated with document editing show “0 Changes”. In the Resource tab, document-content is “Empty”, even though the actual document contains saved text and an image.
  • After appending and persisting the revision paragraph, the latest history entry still shows 0 Changes / Empty document-content. I cannot inspect the earlier or current protocol text through this history UI.
  • The UI offers “Restore this version” for older entries, without explaining that the document text is not visible in this version view. I did not press Restore, so this report does not claim that restoring loses text or that the underlying content history is missing.

Expected result: a researcher should be able to inspect the document's text at a selected revision (and ideally its rich content). If this History screen currently covers resource metadata only, make that limitation clear and direct the user to the document revision history, rather than showing an apparently empty document.

Impact: the History action is difficult to trust for reviewing changes to study notes or experimental protocols. The visible versions do not let me tell what text I would be recovering.

The synthetic note remains saved correctly in the normal editor. This is a report about the history presentation, not an observed loss of the current note.

Dominant language
TypeScript
Stars
1.6k
Forks
82
Avg merge
9h 12m
Merged PRs (30d)
187

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 ontola/atomic-server

All issues in ontola/atomic-server

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.