MerginMaps / MerginMaps/mobile

Filter applied with invalid range input (Number and Date from/to widgets)

Open
#4,503 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

When a Number (from/to) or Date (from/to) filter is configured with an invalid range (Min > Max / From > To), the app shows a validation error but still allows the filter to be submitted. Tapping "Apply filters" applies the filter and returns 0 features instead of blocking submission.

Environment

  • PROD

Application (+ app version, build, operating system)
Mergin Maps iOS 2026.2.0 / iOS 26.4

Steps to reproduce

  1. Open a project with a Number (from/to) filter configured
  2. Open Filters → Number filter → enter Min = 100, Max = 10
  3. Observe the validation error → tap Apply filters
  4. Open the layer features list
  5. Repeat for a Date (from/to) filter → set From = 01/05/2026, To = 20/04/2026 → Apply filters

Actual results

  • Validation error "Min" must be less than "Max" / "From" must be sooner than "To" is shown under both fields with red borders
  • Apply filters button remains active and filter is submitted
  • 0 features returned; "Active filters applied" banner shown in the features list

Expected results

  • Apply filters button should be disabled when a validation error is present
  • Filter should not be submitted until the range is corrected

Screenshots or logs


Conclusion
Created by Claude and supervised by a human test analyst.

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

The issue identifies the Number and Date from/to filter widgets and the Apply filters action, but no source file or test is named. Start by locating the validation and submission handling for these widgets, reproduce both invalid ranges, and verify that submission is blocked until each range is corrected.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, ios
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.