Refactor humanize() method, expand usage, fix edge cases
See original GitHub issue.humanize()
is getting kind of long and could do with refactoring. We’d also like to explore allowing other inputs such as date
and timedelta
objects.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
7 Code Refactoring Techniques in Software Engineering
Mainly we use this technique to reduce the redundancy (duplication) in our code. This involves class inheritances, hierarchy, creating new ...
Read more >5 Refactoring Techniques You Can Use To Improve Your ...
Discover five refactoring techniques to improve your existing code and the primary benefits of each method.
Read more >sails/CHANGELOG.md
- Update boilerplate bootstrap and hook initialize functions. 68, - Disable 'async' dependency when generated the expanded starter app, to avoid confusion. (Can ......
Read more >golang-github-prometheus-prometheus-2.7.1-bp152.3.41
#6880 * Remote Write: Fixed blocked resharding edge case. ... there might be some increase in memory usage, CPU usage, or query latency....
Read more >CFWheels Core
... Ruby on Rails that provides fast application development, a great organization system for your code, and is just plain fun to use....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @olivebay, we’re currently evaluating various ways to improve this. The current method for calculating relative dates relies upon fairly basic math operations and assumptions. Our concern with implementing something more accurate and precise would be reduced performance for batch processing jobs. Most likely we’d either introduce a flag or new method for more precise results (similar to https://www.timeanddate.com/date/duration.html).
Once this is fixed, we should revert coverage requirement to 100%: https://github.com/arrow-py/arrow/issues/749.