-
Notifications
You must be signed in to change notification settings - Fork 52
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
Number normalizer #250
Number normalizer #250
Conversation
I added check for null and empty, where it's possible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hunterlan This is a bit fussy, but can you fix this?
no problem! |
Already been merged tho, LGTM. |
I've meant to use library such as DataSizeUnits. But Our team member already merged and I will work on it. |
@DeveloperWOW64 We should've used something library for this such as 'DataSizeUnits'. |
Why? It's not necessary, current convertor is working well |
Yeah. Of course, Thank you for your contribution. But I didn't want to use helpers but converters. The reason why is easy to convert value on XAML code. |
It is not necessary to add observable strong properties for converted values. Converters on XAML is just able to be converted as you expected with no properties. |
⏱️ Before you start
📄 Description
Added number normalizer helper. It's static class, which can be used everywhere.
Also, I changed a bit repository overview.
💭 Motivation and Context
📸 Assets (if appropriate):