Synopsis

Provides a bit of C# syntactic sugar

Code Example

StringToEnumExtension:

enum MyEnum
{
  One = 1,
  Two = 2
}

string @string = "One";
MyEnum value = @string.Parse<MyEnum>();

DictionaryExtensions:

IDictionary<string, object> dict = null;
dict = dict.NullToEmpty();
var size = dict.Count; // size == 0, no exception here.

IEnumerableExtensions:

new int[] { 1, 2, 3, 4, 5 }
	.TakeProject(
		item => item % 2 == 0,
		item => $"{item} Mississippi"); // ->  { "2 Mississippi", "4 Mississippi" }
		
		
new int[] { 1, 2, 3, 4, 5 }
	.SkipProject(
		item => item > 2,
		item => $"{item} Mississippi"); // ->  { "1 Mississippi", "2 Mississippi" }
		
new int[] { 1, 2 }
	.TakeProjectMany(
		item => item < 2,
		item => new int[] { item, item, item }); // ->  { 1, 1, 1 }
		
new int[] { 1, 2 }
	.SkipProjectMany(
		item => item < 2,
		item => new int[] { item, item, item }); // ->  { 2, 2, 2 }

ArrayExtensions:

string[] array = null;
array = array.NullToEmpty();
var length = array.Length; // length == 0, no exception here.

ListExtensions:

string[] ints = new[] { "Alice", "Bob" };
list.SwapAt(0, 1); // Swaps items in place. The array is now []{ "Bob", "Alice" }

Sequence:

// Other sequence types or even custom sequence generators can be used.
var integers = Sequence
	.WithoutDuplicates(Sequence.NaturalNumbers)
	.Take(5)
	.ToList(); // Results in a List<int>() { 1, 2, 3, 4, 5 }

// Sequence start number and sequence step can be explicitly provided if necessary.

Motivation

Syntax sugar is syntax sugar: it's not a necessary thing per se but it can improve code quality.

Installation

Peppermint is a available in a form of a NuGet package. Follow regular installation process to bring it to your project. https://www.nuget.org/packages/Peppermint/

Tests

Unit tests are available in Peppermint.Tests project.

License

The code is distributed under the MIT license.

Reporting an Issue

Reporting an issue, proposing a feature, or asking a question are all great ways to improve software quality.

Here are a few important things that package contributors will expect to see in a new born GitHub issue:

• the relevant version of the package;
• the steps to reproduce;
• the expected result;
• the observed result;
• some code samples illustrating current inconveniences and/or proposed improvements.

Contributing

Contribution is the best way to improve any project!

1. Fork it!
2. Create your feature branch (git checkout -b my-new-feature).
3. Commit your changes (git commit -am 'Added some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

...or follow steps described in a nice fork guide by Karl Broman