OSOE-751: Upgrade to Orchard Core 1.8

[Psichorex]

OSOE-751
Fixes #638

[coderabbitai]

Walkthrough

This update primarily focuses on upgrading to Orchard Core 1.8, aligning with the latest Orchard Core improvements and API changes. It involves updates to target frameworks, package versions, and subproject commit references across various modules, utilities, and test projects. Additionally, there's a concerted effort to improve asynchronous calls and integrate new Orchard Core features, reflecting a broad enhancement of the project's functionality and compatibility with the latest Orchard Core version.

Changes

Files or Directories	Change Summary
src/.../Lombiq.OSOCE.Web.csproj, test/.../Lombiq.OSOCE.Tests.UI.csproj	Updated TargetFramework to net8.0 and incremented package versions.
src/Modules/..., src/Libraries/..., tools/...	Updated subproject commit references.
.github/workflows/...	Updated GitHub Actions workflow references.
test/.../Tests/ModuleTests/...	Modified constructors to accept ITestOutputHelper and added/modified test assertions.

Assessment against linked issues

Objective	Addressed	Explanation
Upgrade to Orchard Core 1.8 (OSOE-751) [#638]	✅
Utilize new async features from Orchard Core PRs [#638]	❓	The summary does not explicitly mention the utilization of new async features from specified Orchard Core PRs. However, the upgrade to Orchard Core 1.8 likely encompasses these changes indirectly.
Update forms according to Orchard Core PR [#638]	❓	Without specific mention of form updates in the summary, it's unclear if the changes from Orchard Core PR #14806 were applied.
Add release notes about AI setup changes and UI Testing Toolbox [#638]	❌	The provided summary does not include information about updating documentation or release notes.

The overall changes seem to align well with the primary objective of upgrading to Orchard Core 1.8, with some specifics about how new async features and form updates from Orchard Core PRs have been applied remaining unclear from the summary alone. Documentation updates, particularly for release notes, appear to be outside the scope of the provided changes.

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.

[github-actions]

This pull request has merge conflicts. Please resolve those before requesting a review.

[github-actions]

This pull request has merge conflicts. Please resolve those before requesting a review.

[github-actions]

This pull request has merge conflicts. Please resolve those before requesting a review.