Issues • guibranco/CrispyWaffle

Classes implementing `IEquatable<T>` can be `sealed`

CS-R1053

Anti-pattern

Major

3 months ago — 10 months old

Seen in 5 files

5

Use `.TryAdd` to safely add keys to a `Dictionary<K, V`>

CS-R1123

Anti-pattern

Major

3 months ago — 4 months old

Seen in 1 file

1

Type can be dropped from the declaration's RHS when explicitly mentioned in the LHS

CS-R1064

Anti-pattern

Major

3 months ago — 10 months old

Seen in 3 files

10

Consider using `if`-`else` instead of a `switch` statement when having 2 or fewer cases

CS-R1116

Anti-pattern

Minor

3 months ago — 10 months old

Seen in 1 file

1

Consider using `.TryParse` over `.Parse` when converting types

CS-R1004

Anti-pattern

Major

3 months ago — 10 months old

Seen in 1 file

5

Exception caught is generic

CS-R1008

Anti-pattern

Major

3 months ago — 10 months old

Seen in 4 files

5

Consider using the range operator `..` over `Substring`

CS-R1037

Anti-pattern

Major

25 days ago — 10 months old

Seen in 7 files

12

Consider rewriting `using` statement as `using` declaration

CS-R1050

Anti-pattern

Major

3 months ago — 10 months old

Seen in 10 files

12

`Attribute` suffix is redundant when using an attribute

CS-R1075

Anti-pattern

Major

3 months ago — 10 months old

Seen in 1 file

1

Avoid nested ternary expressions

CS-R1114

Anti-pattern

Major

3 months ago — 10 months old

Seen in 1 file

1

Missing `Justification` value in `SuppressMessage` attribute

CS-R1139

Anti-pattern

Critical

25 days ago — 7 months old

Seen in 8 files

10

Fields initialized only in constructors can be made `readonly`

CS-R1137

Anti-pattern

Major

3 months ago — 7 months old

Seen in 1 file

1

Use conditional access operator or pattern matching to safely access nullable value

CS-R1136

Anti-pattern

Major

3 months ago — 7 months old

Seen in 1 file

1

Avoid multiple assignments in a single expression

CS-R1143

Anti-pattern

Major

3 months ago — 7 months old

Seen in 1 file

1

Consider specifying the `CultureInfo` parameter when possible

CS-R1018

Anti-pattern

Major

3 months ago — 10 months old

Seen in 2 files

5

Parameters marked as `in`, `out` or `ref` should always be placed after all the required parameters

CS-R1138

Anti-pattern

Critical

3 months ago — 3 months old

Seen in 1 file

1

Use File Scoped `namespace`s instead of typical `namespace`s

CS-R1062

Anti-pattern

Major

25 days ago — 10 months old

Seen in 142 files

142

`if` statement can be rewritten using the ternary operator

CS-R1105

Anti-pattern

Major

3 months ago — 10 months old

Seen in 3 files

3

guibranco / CrispyWaffle

Classes implementing IEquatable<T> can be sealed

Use .TryAdd to safely add keys to a Dictionary<K, V>

Type can be dropped from the declaration's RHS when explicitly mentioned in the LHS

Consider using if-else instead of a switch statement when having 2 or fewer cases

Consider using .TryParse over .Parse when converting types

Exception caught is generic

Consider using the range operator .. over Substring

Consider rewriting using statement as using declaration

Attribute suffix is redundant when using an attribute

Avoid nested ternary expressions

Missing Justification value in SuppressMessage attribute

Fields initialized only in constructors can be made readonly

Use conditional access operator or pattern matching to safely access nullable value

Avoid multiple assignments in a single expression

Consider specifying the CultureInfo parameter when possible

Parameters marked as in, out or ref should always be placed after all the required parameters

Use File Scoped namespaces instead of typical namespaces

if statement can be rewritten using the ternary operator

Classes implementing `IEquatable<T>` can be `sealed`

Use `.TryAdd` to safely add keys to a `Dictionary<K, V`>

Consider using `if`-`else` instead of a `switch` statement when having 2 or fewer cases

Consider using `.TryParse` over `.Parse` when converting types

Consider using the range operator `..` over `Substring`

Consider rewriting `using` statement as `using` declaration

`Attribute` suffix is redundant when using an attribute

Missing `Justification` value in `SuppressMessage` attribute

Fields initialized only in constructors can be made `readonly`

Consider specifying the `CultureInfo` parameter when possible

Parameters marked as `in`, `out` or `ref` should always be placed after all the required parameters

Use File Scoped `namespace`s instead of typical `namespace`s

`if` statement can be rewritten using the ternary operator