@mgnslndh Did you try the metric converter? Does it fit your needs? How can it be improve?

I'd like to suggest a way to limit the range of prefixes used, let's suppose we are trying to humanize distances

100d.ToMetric() + "m";   //Result: 100m
2000d.ToMetric() + "m";  //Result: 2km
5000000d.ToMetric() + "m" //Result: 5Mm

The last result is not very useful, a Megameter is a SI unit, but i'd rather have 5000km as a result

I've just started implementing this request, as my first contribution to an open source project!

My current plan is to add an optional parameter to ToMetric named largestPrefix. Setting it to a new enum MetricPrefix will place an upper limit to the used prefix.

I got some questions that I hope you can help me with:

1. As you know, naming is hard. Do you got any suggestions for the parameter name you feel is better than largestPrefix ?
2. Would there be a use for a corresponding smallestPrefix option? I like it for symmetry but I can't think of any common real world use cases.
3. The contribution instruction references the dev branch. I can't find any general and up to date dev branch. Should it be master?
4. I do not got access to ReSharper. How do you suggest I satisfy the requirement to have no ReSharper warnings?
5. I'm unsure of when to end a sentence with a period and when to leave it out in the Xml documentation. What are the rules?
6. The use of copyright notices in individual files seems to vary wildly. Is there a recommended way in to do it in this project?

Thank you for any help with my questions, or other suggestions for an open source noob! :)

(Edit: Changed parameter type to enum.)

My current names are maxPrefix and minPrefix. Short and max/min is very common in programming.

@JonasBarka Your comment make me think that you could open an issue about your contribution question. This issue could result in a PR to the Contribute.md file. :)