[FORM-4] Form macro throws null pointer if question is null Created: 16/Nov/22 Updated: 21/Dec/22 Resolved: 16/Nov/22 |
|
| Status: | Closed |
| Project: | FORM |
| Component/s: | None |
| Affects Version/s: | 1.1.1 |
| Fix Version/s: | 1.1.2 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Raphael Falvo |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Team: | |||||
| Description |
|
Error message: The following has evaluated to null or missing: ==> question.rangeFrom [in template "form-core/macros/form.ftl" at line 90, column 51] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use [#if myOptionalVar??]when-present[#else]when-missing[/#if]. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- Add null check for question. |