Skip to content

Commit 84f39b6

Browse files
fix readme
1 parent a557b85 commit 84f39b6

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

README.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# ![](Icon.png) Lambda Converters
1+
# <img src="Icon.png" width="48" height="48" /> Lambda Converters
22

33
The library allows to write `IValueConverter` and `IMultiValueConverter` objects with the most convenient syntax available, ideally, using the lambda expressions.
44

@@ -13,7 +13,8 @@ internal static class Converters
1313
public static readonly IValueConverter VisibleIfNotNull =
1414
ValueConverter.Create<object, Visibility>(e => e.Value != null ? Visibility.Visible : Visibility.Collapsed);
1515

16-
public static readonly IValueConverter ToUpperCase = ValueConverter.Create<string, string>(e => e.Value.ToUpper());
16+
public static readonly IValueConverter ToUpperCase =
17+
ValueConverter.Create<string, string>(e => e.Value.ToUpper());
1718
}
1819
```
1920

@@ -31,7 +32,7 @@ You're done! Just reference the converters with the `x:Static` expressions from
3132
- separate class for each converter not needed anymore
3233
- no redundant declarations: if you do not need the `ConvertBack` method, don't define it; otherwise, just put the second lambda expression
3334
- full support for the remaining parameters of the `Convert` and `ConvertBack` methods: the `culture` and the `parameter` (also strongly-typed) are accessible as well
34-
- if the conversion fails due to unexpected value types the optional [error strategy](LambdaConverters.Wpf/ConverterErrorStrategy.cs) can be specified
35+
- if the conversion fails due to unexpected value types the optional [error strategy](Sources/LambdaConverters.Wpf/ConverterErrorStrategy.cs) can be specified
3536

3637
:bulb: *ReSharper users*: use the Extension Manager to install the external annotations for the library.
3738

0 commit comments

Comments
 (0)