Development: Refactor deprecated usage of throwError

[MaximilianAnzinger]

Checklist

General

• I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

export declare function throwError(error: any): Observable<never>; is deprecated and should therefore be replaced by export declare function throwError(errorFactory: () => any): Observable<never>;

Review Progress

Code Review

• Code Review 1
• Code Review 2

Summary by CodeRabbit

• Tests
  • Enhanced error handling in several service calls across different components.
  • Improved readability and clarity in test specifications through better formatting and structure adjustments.
  • Updated test setups to use more dynamic response handling for error scenarios.

[coderabbitai]

Walkthrough

The recent modifications across various test specifications primarily focus on refining error handling and improving code readability. Changes include the adoption of arrow functions for error generation, enhancing the structure of mock return values, and reformatting object declarations for clarity. These adjustments ensure more robust and maintainable test suites, aligning with best practices in error management and code presentation.

Changes

File Path	Changes Summary
Various files in .../course-registration/ and .../programming-exercise/	Updated error handling to use arrow functions for generating HttpErrorResponse.
Various files in .../course/, .../lecture/, and .../participation/	Enhanced readability with improved formatting and structure in object declarations and mock return assignments.
.../iris/ related service specs	Adjusted error handling by modifying HttpErrorResponse creation within jest.spyOn calls.
.../text-exercise/... and .../shared/metis/...	Updated error handling syntax in service methods and function calls.

---

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 testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• 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 testing code 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 and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @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.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[rabeatwork]

Thank You!

[coderabbitai]

Actionable comments posted: 9

[julian-christl]

Changes look good, and Coderabbit is drunk.