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

Automatically save/autosave the user's work in the form editor after every change

Open
  • Is something wrong?
#418 0 comments 1 reaction 1 assignee View on GitHub

Maintainers usually reply within 1 day

@earth-walker is already working on this.

Since May 5, 2026.

Assessment

This issue has not been assessed yet.

Description

big lift

I think that automatically saving the user's work in the form editor after every change they make would be a better workflow than clicking the save button to save their work.

I notice that in practice, most users click the save button after every change they make.

Not autosaving also allows for the possibility of accidentally losing work by closing the project before saving.

If we implement autosaving, we should also implement a versioning system where you can "save as" to create a version of the project and then continue working, then switch to the other version as needed. This will require some UX and technical thinking to develop.

@prestoncabe mentioned that this might require grouping the entire screener project into one object, which sounds like a good idea to me.

Dominant language
Java
Stars
16
Forks
5
Avg merge
1d 26m
Merged PRs (30d)
25

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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 CodeForPhilly/benefit-decision-toolkit

All issues in CodeForPhilly/benefit-decision-toolkit

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.