V3191. Iteration through collection makes no sense because it is always empty.
V3191 Iteration through the 'fields' collection makes no sense because it is always empty. SqlServerStatementBuilder.cs 70
public override string CreateBatchQuery(string tableName,
IEnumerable<Field> fields,
int page,
int rowsPerBatch,
IEnumerable<OrderField> orderBy = null,
QueryGroup where = null,
string hints = null)
{
// Ensure with guards
GuardTableName(tableName);
// Validate the hints
GuardHints(hints);
// There should be fields
if (fields?.Any() != true)
{
throw new MissingFieldsException(fields?.Select(f => f.Name)); // <=
}
....
}
V3191 Iteration through the 'results' collection makes no sense because it is always empty. ConVarSystem.AutoComplete.cs 23
public static ConCmdAttribute.AutoCompleteResult[]
GetAutoComplete(....)
{
var parts = partial.SplitQuotesStrings();
List<ConCmdAttribute.AutoCompleteResult> results = new();
// if we have more than one part, complete a specific command
if ( parts.Length > 1 )
{
if ( !Members.TryGetValue( parts[0], out var command )
return Array
.Empty<ConCmdAttribute.AutoCompleteResult>();
//results.Add( new ConCmd.AutoCompleteResult
// { Command = command.Name, Description = command.Help } );
// TODO - dig into it for auto complete
return results.Take( count ).ToArray();
}