MerginMaps / MerginMaps/mobile

Stack of relations forms

Open
#2,329 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug forms
Dominant language
C++
Stars
388
Forks
87
Avg merge
2d 7h
Merged PRs (30d)
20

Description

I can create stack of features forms for 1-N relations features and they are available to edit, even then they are deleted.

Scenario:

  1. open tc04_relations project
  2. create and distring and add at least one natural to it and save both
  3. then open the district and click on the natural -> this opens form of the natural
  4. now click on the district -> this will open form of the district
  5. now click on the natural again -> this opens form of the district
  6. repeat this multiple times and stop on the district form
  7. now remove the district and confirm the deletion
    -> now you can see that in the natural form, district is still visible
  • when you hit it, the already deleted district opens an you can edit it (add naturals .. ) but when you save it nothing happens
  • when you hit arrow in the top left corner, you will go though the stack of forms back for even deleted feature.

https://user-images.githubusercontent.com/83582181/196796783-d285b472-e238-4da4-830c-5bdac40a50fb.mp4

Contributor guide

Open the 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.

Research direction

Start by reproducing the stack-of-forms scenario in the tc04_relations project, following the numbered steps and reviewing the linked video. Confirm that deleting the district removes it from the natural form and that back navigation no longer reaches deleted forms; the payload names no source files or tests.

Written by the indexing model from the issue text.

Assessment

Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.