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

Say in the admin that a field delete and a carry reach content the group left

Open
  • Is something wrong?
#372 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
62/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
go, react, typescript
Domain
frontend, internationalization

Research direction

Start with the delete warning in frontend/src/content/GroupFieldsDialog.tsx and the two carried-field move lines in frontend/src/content/ImportDefinitions.tsx, then read how the test in frontend/src/test/definitions-import.test.tsx asserts the import line. Update the English strings to describe the new reach, add the Spanish and French entries in frontend/src/languages and internal/i18n/catalogs marked fuzzy, and run the import test to confirm it is done.

Written by the indexing model from the issue text.

Description

help wanted

The admin still describes the old reach of a field delete and of a carried field.

  • The delete dialog says the values go "in every item the group reaches". A delete now also clears the value on content the group stopped reaching when its rules changed, wherever no active group serves that place.
  • The import screen says a carried field "keeps its stored values". A carry now also clears the values the field left on content neither group reaches.

What to change:

  • frontend/src/content/GroupFieldsDialog.tsx: the delete warning.
  • frontend/src/content/ImportDefinitions.tsx: the two carried move lines, for example "It moves to another group and keeps its values on the content both groups reach."
  • The Spanish and French catalogs in frontend/src/languages and internal/i18n/catalogs, with the new machine translations marked fuzzy.
  • frontend/src/test/definitions-import.test.tsx, which checks the import line.
Dominant language
Go
Stars
293
Forks
50
Avg merge
16h 58m
Merged PRs (30d)
124

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No 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.

More from gopherium/gophenberg

All issues in gopherium/gophenberg

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.