Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Outdated “current” year
See original GitHub issueBug report
What’s wrong
Some providers return “current” dates from a few years ago, because they are hardwired to the “current” year from those times, such as:
mimesis.Datetime().week_date()mimesis.Datetime().date()mimesis.Development().version(calver=True)PolandSpecProvider().pesel()
How is that should be
Having a global now would break a lot of things, because with the same seed, we would get different results at each run.
Then maybe changing mimesis’ versioning to calver and do such updates of default year with every major version? This would allow adding methods like birthdate to the Person provider as well.
System information
Not relevant.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It looks good. And it will return the same value within one year, which is probably okay for your users.
I think it will work with seed as well because
date().yearwill always return the same value.