Skip to content

feat: updated LLamaSharp to 0.7, updated examples (#46) #99

feat: updated LLamaSharp to 0.7, updated examples (#46)

feat: updated LLamaSharp to 0.7, updated examples (#46) #99

Triggered via push November 4, 2023 16:50
Status Success
Total duration 4m 22s
Artifacts 1

dotnet.yml

on: push
Build, test and publish  /  Build, test and publish
4m 10s
Build, test and publish / Build, test and publish
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Build, test and publish / Build, test and publish: src/libs/LangChain.Core/TextSplitters/RecursiveCharacterTextSplitter.cs#L60
Prefer comparing 'Count' to 0 rather than using 'Any()', both for clarity and for performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1860)
Build, test and publish / Build, test and publish: src/libs/LangChain.Core/TextSplitters/RecursiveCharacterTextSplitter.cs#L72
Prefer comparing 'Count' to 0 rather than using 'Any()', both for clarity and for performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1860)
Build, test and publish / Build, test and publish: src/libs/LangChain.Core/Docstore/Document.cs#L30
Prefer 'static readonly' fields over constant array arguments if the called method is called repeatedly and is not mutating the passed array (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1861)
Build, test and publish / Build, test and publish: src/libs/LangChain.Core/Docstore/Document.cs#L46
Prefer using 'string.Equals(string, StringComparison)' to perform a case-insensitive comparison, but keep in mind that this might cause subtle changes in behavior, so make sure to conduct thorough testing after applying the suggestion, or if culturally sensitive comparison is not required, consider using 'StringComparison.OrdinalIgnoreCase' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1862)
Build, test and publish / Build, test and publish: src/libs/LangChain.Core/Docstore/Document.cs#L57
Prefer the string comparison method overload of 'string.Contains(string)' that takes a 'StringComparison' enum value to perform a case-insensitive comparison, but keep in mind that this might cause subtle changes in behavior, so make sure to conduct thorough testing after applying the suggestion, or if culturally sensitive comparison is not required, consider using 'StringComparison.OrdinalIgnoreCase' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1862)
Build, test and publish / Build, test and publish: src/libs/LangChain.Core/Docstore/Document.cs#L46
In method 'Lookup', replace the call to 'ToLower' with 'ToUpperInvariant' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1308)
Build, test and publish / Build, test and publish: src/libs/LangChain.Core/Docstore/Document.cs#L48
In method 'Lookup', replace the call to 'ToLower' with 'ToUpperInvariant' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1308)
Build, test and publish / Build, test and publish: src/libs/LangChain.Core/Docstore/Document.cs#L57
In method 'Lookup', replace the call to 'ToLower' with 'ToUpperInvariant' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1308)
Build, test and publish / Build, test and publish: src/libs/LangChain.Core/TextSplitters/RecursiveCharacterTextSplitter.cs#L60
Prefer comparing 'Count' to 0 rather than using 'Any()', both for clarity and for performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1860)
Build, test and publish / Build, test and publish: src/libs/LangChain.Core/TextSplitters/RecursiveCharacterTextSplitter.cs#L72
Prefer comparing 'Count' to 0 rather than using 'Any()', both for clarity and for performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1860)

Artifacts

Produced during runtime
Name Size
nuget-packages Expired
6.15 MB