OSOE-751: Upgrade to Orchard Core 1.8

[Psichorex]

OSOE-751

[coderabbitai]

Walkthrough

This update primarily focuses on transitioning the Lombiq.Tests.UI project and its related components to target .NET 8.0, updating OrchardCore package references, and improving code quality and performance. Key changes include adopting new C# features such as the spread operator for array initialization, utilizing string.Create for efficient string concatenation, and refining method return types and class fields for better clarity and functionality. Additionally, it enhances logging and error handling mechanisms, aligns with OrchardCore 1.8 requirements, and updates GitHub Actions workflows for more precise branch referencing.

Changes

File Path	Change Summary
Lombiq.Tests.UI/.../*.csproj	Updated target framework to net8.0 and OrchardCore packages to 1.8.2.
Lombiq.Tests.UI/MonkeyTesting/MonkeyTester.cs	Added System.Globalization, improved list and array initialization, optimized string operations, and refactored error handling.
Lombiq.Tests.UI/Extensions/ShortcutsUITestContextExtensions.cs	Modified PurgeMediaCacheDirectlyAsync method and refactored ExecuteRecipeShortcut class. Updated IsAdminTheme method.
Lombiq.Tests.UI/Extensions/ExtendedLoggingExtensions.cs	Changed ExecuteSectionAsync return type to Task<bool>.
Lombiq.Tests.UI/Services/...	Updated SqlServerManager and UITestExecutionSession for better compatibility and coding practices.
.github/workflows/publish-nuget.yml	Updated workflow file to use specific branch or issue reference.
Lombiq.Tests.UI/UITestBase.cs	Removed unnecessary pragma directives.

Related issues

• Upgrade to Orchard Core 1.8 (OSOE-751) Open-Source-Orchard-Core-Extensions#638: The updates align with the objectives of upgrading to Orchard Core 1.8 by updating package references and improving code to utilize new features and better practices. This indicates the changes in this PR are directly contributing to the upgrade process and enhancements mentioned in the issue.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[Piedone]

See #338 (comment).

[Psichorex]

This is intentionally not upgraded because it would introduce more html-validation warnings mainly probably coming from OC source.