kir-dev / kir-dev/cmsch

The new order of the fields in a form are only saved if something else has changed

Open
#647 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

BACKEND bug
Dominant language
Kotlin
Stars
25
Forks
6
Avg merge
1d 23h
Merged PRs (30d)
9

Description

If you start editing a form with multiple fields, then change the order of the fields, then save, the new order is not saved. If you change anything else on the form, every change (including the new order) is saved

Contributor guide

No contributing guide indexed for this repository

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

Reproduce the issue by editing a form with multiple fields, changing only their order, and saving; then compare it with a save that includes another form change. Trace the form editing and persistence entry points to find why order-only changes are skipped, and consider the issue done when reordered fields remain in the new order after saving without other edits.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin, react, spring-boot
Domain
full-stack
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.