That's cromulent but, at least from the limited original description, quite different from the OP's problem; a script specifically to write temporal output versus a script only intended (for the time being at least) to run within a temporal window. The second is the sort of thing that is harder to debug and circumvent on demand as well. Taking date args in the invocation would be better than hardcoding the date in all invocations. So I say. :P
| [reply] [Watch: Dir/Any] |
I think that better than taking date args, taking behavior-shaping args is probably preferable. Let the caller decide what behavior is desired for a given date, alignment of the stars, unforeseen business need, or temperature in Bermuda.
Of course this is only an opinion, and one that has been formulated with less than the full set of facts for this specific use case. :)
| [reply] [Watch: Dir/Any] |