revert code

[iceljc]

PR Type

Other

---

Description

• Reverted collection types from IEnumerable to List

• Changed three properties in vector storage models

---

Diagram Walkthrough

flowchart LR
  A["VectorFilterGroup"] --> B["Filters: IEnumerable → List"]
  C["VectorFilterSubGroup"] --> D["Operands: IEnumerable → List"]
  E["VectorFilterRange"] --> F["Conditions: IEnumerable → List"]

Loading

File Walkthrough

	Relevant files
Miscellaneous	VectorFilterGroup.cs Revert collection types to concrete List implementations  src/Infrastructure/BotSharp.Abstraction/VectorStorage/Models/VectorFilterGroup.cs Changed Filters property from IEnumerable to List Changed Operands property from IEnumerable to List Changed Conditions property from IEnumerable to List +3/-3

---

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review API Contract Change Changing properties from IEnumerable to List alters the public contract and may break callers relying on broader interfaces or deferred execution. Validate all callers, serialization formats, and ensure backward compatibility where needed. public List<VectorFilterSubGroup>? Filters { get; set; } Nullability Consistency Filters is nullable while Operands and Conditions are non-null with empty defaults. Confirm intended nullability across these collections to avoid inconsistent handling and potential NREs when Filters is null. public List<VectorFilterSubGroup>? Filters { get; set; }

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Initialize list to avoid null Using a nullable list property can cause null-reference issues for consumers expecting an empty collection. Initialize the list to an empty list to ensure safe iteration and serialization consistency. src/Infrastructure/BotSharp.Abstraction/VectorStorage/Models/VectorFilterGroup.cs [8] -public List<VectorFilterSubGroup>? Filters { get; set; } +public List<VectorFilterSubGroup> Filters { get; set; } = new(); Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies a nullable list property Filters that should be initialized to prevent potential NullReferenceException, which is a good practice for collection properties.	Medium
General	Replace '[]' with 'new()' The target framework may not support the collection expression '[]', risking compilation issues. Use 'new()' for broader compatibility and clarity. src/Infrastructure/BotSharp.Abstraction/VectorStorage/Models/VectorFilterGroup.cs [17] -public List<VectorFilterOperand> Operands { get; set; } = []; +public List<VectorFilterOperand> Operands { get; set; } = new(); Apply / Chat Suggestion importance[1-10]: 4 __ Why: The suggestion correctly points out that using the [] collection expression might cause compatibility issues with older C# versions and suggests the more widely compatible new() syntax.	Low
	Use compatible list initialization Avoid the collection expression if older language versions are in use and ensure consistent initialization. Replace with 'new()' to reduce language-version dependency. src/Infrastructure/BotSharp.Abstraction/VectorStorage/Models/VectorFilterGroup.cs [55] -public List<VectorFilterRangeCondition> Conditions { get; set; } = []; +public List<VectorFilterRangeCondition> Conditions { get; set; } = new(); Apply / Chat Suggestion importance[1-10]: 4 __ Why: The suggestion correctly points out that using the [] collection expression might cause compatibility issues with older C# versions and suggests the more widely compatible new() syntax.	Low
More