TypeError with 6.2.0

Mobile Apps Bugs
21

I should probably normalize the values to iso datestrings instead of having the date objects being returned. Will post an update later that will create a valid values for App Connect. The expression {{f7calendar1.value[1]}} should indeed return the second date, not sure what goes wrong there, perhaps the update will fix it.

22

Here the new update: dmxFramework7.zip (106.5 KB)

23

Thanks, now:
<p>{{f7calendar1.value[0].formatDate('dd/MM/yyyy')}}</p>
and
<p>{{f7calendar1.value[1].formatDate('dd/MM/yyyy')}}</p>
Works.

But {{f7calendar1.value}}
image
And
{{f7calendar1.value.formatDate('dd/MM/yyyy')}}
doesn’t work, so for a single date we need to manually add [0].

Maybe it would be good to leave it written down for those who want to try the component.
Since it is an array,we need to specify [0] for a single date.

The correct code of toggle does the trick.
I’ll keep testing :slight_smile:

Thanks again for all your dedication on this stuff!

24

The .value is always an array, so when you want to get the date you always have to access it by index.

Calendar / Datepicker | Framework7 Documentation

I know arrays are difficult to work with in the Wappler UI, perhaps @George can think of an easier way on how to pick values from an array object.