Fix the INTERVAL object operator on a form: the module fails to load with an internal error
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
The payload gives no source file or test path; start by searching the platform sources for the INTERVAL operator and the NF COLLECTION RESTARTED error, then trace the form property parsing path. Reproduce the supplied FORM f example with dryRun and compare it with a working property. Done means the form loads and displays the interval, with range editing when both objects are in a panel.
Written by the indexing model from the issue text.
Description
Description
Adding the INTERVAL object operator for a pair of date objects to a form makes the whole logic fail to load — not with a semantic error but with an internal exception reported at the PROPERTIES line:
FORM f
OBJECTS dates = (d1 = DATE, d2 = DATE) PANEL
PROPERTIES period 'Period' = INTERVAL(d1, d2)
;
// Error during parsing at f:3:4
// java.lang.RuntimeException: NF COLLECTION RESTARTED
Every variant fails the same way: with or without PANEL, with or without an alias and caption, as the first property of the form or after other properties, in its own PROPERTIES statement or together with other groups' properties. Reproduced with dryRun on 7.0-SNAPSHOT (the 2026-10-18 build and the current master sources).
Reason
The operator is documented (Interactive_view, Properties_and_actions_block) as the way to get an editable date-range picker for a pair of panel objects, and it cannot be used at all: the only workaround is two VALUE() properties, which loses the range picker.
Fix
A form with INTERVAL(d1, d2) loads, shows the interval between the two objects and, when both are in a panel, lets the user edit it as a date range, as documented.
- Dominant language
- Java
- Stars
- 214
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lsfusion/platform
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Open a form with a TSQUERY propertyPossibly taken @ichavchavadze claimed this today. Open
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 76/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in lsfusion/platform
Similar issues
-
account bug exercise lecture programming user interface
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ls1intum/Artemis#14512 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
swiftlang/swift-java#955 ·
Maintainers usually reply within 1 day
-
Good First Issue
Difficulty 1/5 Under an hour Newbie friendliness 68/100
hiero-ledger/hiero-sdk-java#3044 ·
Maintainers usually reply within 1 day
-
A second build without clean fails in resources-optimizer-maven-plugin because minified files are minified againPossibly taken @papegaaij claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
hermes-queue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
chrisalunlloyd2-sudo/mindpalace#337 ·
Maintainers usually reply within 1 day