MerginMaps / MerginMaps/mobile

Format_Date in Mergin Input doesn't follow QGIS doc. It saves MMMM instead of MMM

Open
#2,748 0 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

Format_Date in Mergin doesn't follow QGIS doc.

If you use a format_date( now() ,'d MMM yyyy') (with 3 Ms) in your field widgets, QGIS will store it as:

MMM | the abbreviated localized month name (e.g. ‘Jan’ to ‘Dec’)

as described in
https://docs.qgis.org/3.28/en/docs/user_manual/expressions/functions_list.html#format-date

However, Mergin Maps stores it as the long localized month name (e.g. ‘January’ to ‘December’), as if you had configured it as:
format_date( now() ,'d MMMM yyyy') (with 4 Ms)

Tested on iPad and Android Galaxy phone

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 format_date( now() ,'d MMM yyyy') on Android or iOS and compare the result with the linked QGIS documentation. Trace the mobile implementation of date-format handling, then verify that MMM produces an abbreviated localized month while MMMM remains the long form.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, cpp, ios
Domain
localization, mobile-dev
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.