Skip to content

Commit 69201fc

Browse files
committed
Docs: Change the param timeResolution to precision (closes #84)
1 parent 1ee58b1 commit 69201fc

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,7 @@ Type: `Boolean`
122122

123123
Default: `false`
124124

125-
### `lastRun(task, [timeResolution])`
125+
### `lastRun(task, [precision])`
126126

127127
Takes a string or function (`task`) and returns a timestamp of the last time the task
128128
was run successfully. The time will be the time the task started.
@@ -133,7 +133,7 @@ If a task errors, the result of `lastRun` will be undefined because the task
133133
should probably be re-run from scratch to get into a good state again.
134134

135135
The timestamp is always given in millisecond but the time resolution can be
136-
rounded using the `timeResolution` parameter. The use case is to be able to compare a build time
136+
rounded using the `precision` parameter. The use case is to be able to compare a build time
137137
to a file time attribute. On node v0.10 or with file system like HFS or FAT,
138138
`fs.stat` time attributes like `mtime` precision is one second.
139139

0 commit comments

Comments
 (0)