MerginMaps / MerginMaps/mobile

Recursuive apply on default update

Open
#3,363 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

There is a problem with a scenario, when there is recursive apply on default update on multiple fields. I have one field with "apply on default update" and another one, which the same and is controlled by the previous field.

In the tc05_forms_derived, there is a tab Data. It is hidden till something is filled into Value on the Information tab.
On the Data tab, there are 4 fields:

  1. Population (sets population of bears in Slovakia)
  2. Limit (sets limit, till somebody from Slovakia parliament is going to do about it)
  3. Danger is the first field with "apply on default update" sets with value "Population" > "Limit"
  4. Name is the 2nd field, which is controlled by the Danger field and has "apply on default update" set with if("Danger" IS 'false',' Bear safe',' Bear dangerous')

This means, that when Population is > than Limit, the Danger should be true, and Name should be Bear dangerous. This is not happening and because of it, the Slovak parliament doesn't know what to do with it.

In the video, you can see that the update of the Name field is delayed and with the next update has the correct value from the previous data update.

Please note: if you are not familiar with conflicts between bears and politicians in Slovakia, you can freely ignore all the comments on this topic :)

https://github.com/MerginMaps/mobile/assets/83582181/988be761-900d-42f8-b920-0f11e39a2c4f

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

Reproduce the scenario in tc05_forms_derived: fill Value on the Information tab, then update Population and Limit on the Data tab while observing Danger and Name. Done means Name updates during the same data update and shows the value corresponding to the current Danger state. No source file or test path is named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
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.