Add 'now' variable to Snowfakery #485
Conversation
| b: ${{now}} | ||
| """ | ||
| generate(StringIO(yaml), {}, None) | ||
| assert datetime.fromisoformat(generated_rows.table_values("A", 0, "a")) |
There was a problem hiding this comment.
This test seems a little imprecise -- it's verifying that now generates a date, but it doesn't verify that it sets the correct date. Would it be worth taking the time to mock out datetime.now?
docs/index.md
Outdated
| #### `now` | ||
|
|
||
| The `now` variable returns a datetime | ||
| representing the current moment. Experimentally, |
There was a problem hiding this comment.
Would it make sense to specifically mention that this returns the value of datetime.now()? I don't don't if the target audience is savvy enough to know what that means.
There was a problem hiding this comment.
I think not, in general. I'll see what Peter says.
prescod
force-pushed
the
feature/now-function
branch
from
7eed778 to
1d6cae0
Compare
prescod
added
the
doc review needed
|
I addressed David's suggestion that the date have a timezone in d657218. Since this PR was created, Snowfakery adopted a UTC-default policy. |
| The `today` variable returns a date representing the current date. This date does not change chanage during the execution of a single recipe. | ||
| The `today` variable returns a date | ||
| representing the current date. This date | ||
| will not chanage during the execution of |
There was a problem hiding this comment.
| will not chanage during the execution of | |
| doesn't change during the execution of |
| current_datetime_without_microseconds: ${{int(now.timestamp())}} | ||
| ``` | ||
|
|
||
| This would generate field values similar to these: |
There was a problem hiding this comment.
| This would generate field values similar to these: | |
| The above example generates field values similar to these: |
The
nowvariable returns a datetime representing the current moment. It stores microsecond precision.