Skip to content

Commit 837460e

Browse files
committed
rephrase
1 parent b95f499 commit 837460e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/guide/usage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ console.log(firstRandom === secondRandom);
112112
When upgrading to a new version of Faker, you may get different values for the same seed, as the underlying data (lists of names, words etc) may have changed.
113113
:::
114114

115-
There are a few relative date methods for which setting a random seed is not sufficient to have reproducible results, specifically: `faker.date.past`, `faker.date.future`, `faker.date.birthdate`, `faker.date.recent` and `faker.date.soon`. This is because these methods default to creating a date before or after "today", and "today" depends on when the code is run. To fix this, you can specify a fixed reference date as a Date or string, for example:
115+
There are a few methods which use relative dates for which setting a random seed is not sufficient to have reproducible results, for example: `faker.date.past`, `faker.date.future`, `faker.date.birthdate`, `faker.date.recent`, `faker.date.soon` and `faker.git.commitEntry`. This is because these methods default to creating a date before or after "today", and "today" depends on when the code is run. To fix this, you can specify a fixed reference date as a Date or string, for example:
116116

117117
```ts
118118
// creates a date soon after 2023-01-01

0 commit comments

Comments
 (0)