Adds Year and Month support to Duration #53
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hmm, tests are failing due to something unrelated. Don't worry about it. Looks good to me, thank you for your contribution! I have some CI stuff to clean up before making a new release, but I'll try to do so Soon ™️ . |
OliverHofkens
approved these changes
Jun 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We need support for durations specified in Years and Months. Currently, the implementation supports durations up to days. This PR adds Year and Month support as shown below:
SQLAlchemy and Django use timedelta, which doesn't support durations larger than days. I've used average days for a year (365.25) and a month (30.44). This isn't entirely accurate but might be sufficient.