You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/// <summary>Identifies the <see cref="SomeDependencyProperty"/> dependency property.</summary>
public static readonly DependencyProperty SomeDependencyPropertyProperty=
DependencyProperty.Register(nameof(SomeDependencyProperty), typeof(bool), typeof(Whatever), new PropertyMetadata(false));
Reformatting (with R# or any other tool) to
/// <summary>
/// Identifies the <see cref="SomeDependencyProperty" /> dependency property.
/// </summary>
public static readonly DependencyProperty SomeDependencyPropertyProperty=
DependencyProperty.Register(nameof(SomeDependencyProperty), typeof(bool), typeof(Whatever), new PropertyMetadata(false));
triggers the warning again. Even altering the whitespace from the code fix, i.e.
/// <summary> Identifies the <see cref="SomeDependencyProperty"/> dependency property. </summary>
does so.
Whitespace and Newlines shouldn't be triggering the analyzer as long as the string is correct. For comparison SA1624, which is the same for ctor documentation, allows this, as long as the text matches the one required by the analyzer.
The text was updated successfully, but these errors were encountered:
Sorry about this. While this analyzer is not very useful it was a bit of pain to write, the syntax tree for a doc comment is huge.
My thinking was I wanted single line for autogenerated doc comments to make them show as autogenerated.
Not sure when I will have time to fix this, thanks for reporting!
Workaround is to keep whitespace as the analyzer wants it or of course disable the analyzer as it is not very useful. You could set it to hidden to get the code gen but no warnings.
The code fix for WPF0060 produces this code:
Reformatting (with R# or any other tool) to
triggers the warning again. Even altering the whitespace from the code fix, i.e.
does so.
Whitespace and Newlines shouldn't be triggering the analyzer as long as the string is correct. For comparison SA1624, which is the same for ctor documentation, allows this, as long as the text matches the one required by the analyzer.
The text was updated successfully, but these errors were encountered: