-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added Support for Duration Objects. #417
base: develop
Are you sure you want to change the base?
Conversation
These are simply cleaner to work with. Yes you can convert them to millseconds but honestly if there is already a timeunit option a duration option should exist too.
Added tests for them to assure the logic works the exact same. From my side the PR is finished. |
Please, pay attention to code style accepted in the project. |
@kokorin yep already did. |
@kokorin I think the code quality filter you have setup is extremely picky. I went out of my way to make these patches and provided them in a reasonable state. Anything extra is for you to uphold. If you don't want to do that and think that mentality is unreasonable, then please close both prs. |
@kokorin please provide a choice. |
Already did |
Yeah, and at this point you lost me. Anyways, I work with my fork instead of helping. Ignoring this issue. |
Small fun fact, @kokorin Eclipse, my choice of IDE doesn't support Editor configs so in other words: I can't apply your style configs at all. In other words unless I am switching the IDE, which i am not willing to, that style check won't be completed. So yeah, the question comes again: |
Simple support for Duration Objects.
Since they are cleaner to work with than milliseconds directly or using weird number * timeunit multiplications.
Not saying they are bad, but Duration objects are just cleaner to work with due to their helper functions.
I included tests and ran them with no errors.
Though the drawTextWithSpecialCharacters tests fails on both PRs i made so far.