Now... similar question for Lucee. On <https://doc...
# documentation
a
Now... similar question for Lucee. On https://docs.lucee.org/reference/tags/schedule.html we have these two bits of conflicting information:
starttime [...] Enter a value in seconds.
And:
startTime="12:00 AM"
And in our code we're passing
00:05
which seems to work. Can we get the description of that tightened up a bit? I presume it's "a string that can be interpreted as the time part of a datetime"? Or something like that? Maybe something like "A time in one of these formats: HH:mm, h:mmtt [etc]"
z
the magic is happening here, like a lot of cfml, it tries hard to understand whatever input is provided https://github.com/lucee/Lucee/blob/6.0/core/src/main/java/lucee/runtime/op/date/DateCaster.java#L686
a
Yep, cool: cheers for steering me there. My point was more the docs should say, rather than needing to go check the code.
So it'll take a time-ish sort of thing?
z
more or less ish
a
heh. ish
So the "Enter a value in seconds" is def wrong. And I could put "either a DateTime object, or a string that Lucee can interpret as a time, eg
14:00
or
2:00PM
etc)"
e
I am trying to remember how I managed to sort through that... I did a UI for them some time ago as a cmdbox module, and I had to go through all this for date/time: https://github.com/evagoras/lucee-scheduled-tasks/blob/master/models/taskDto.cfc#L98-L185