Development: Update client documentation to use standalone components

[JohannesWt]

Checklist

General

• This is a small issue that I tested locally and was confirmed by another developer on a test server.
• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

As discussed today in the dev meeting we will use standalone components from now on for new components. Old components should be migrated step by step (evaluated case by case)

Description

This PR updates the client documentation to use standalone components.
Changed documentation https://artemis-platform--8678.org.readthedocs.build/en/8678/dev/guidelines/client.html#components

Testserver States

Note

These badges show the state of the test servers.
Green = Currently available, Red = Currently locked

Review Progress

Code Review

• Code Review 1
• Code Review 2

Test Coverage

[coderabbitai]

Walkthrough

The recent updates to the client.rst guidelines focus on promoting the creation of standalone components in Angular. These components should encapsulate their logic, view, and styles independently. The document now also includes a command for generating these components using Angular CLI and suggests a gradual migration of existing components to this new structure to ensure continued functionality.

Changes

Files	Change Summary
docs/dev/guidelines/client.rst	Emphasized creating standalone components in Angular, provided migration suggestions, and CLI command.

Sequence Diagram(s) (Beta)

sequenceDiagram
    participant Developer
    participant AngularCLI
    participant Component
    Developer->>AngularCLI: Generate standalone component
    AngularCLI-->>Developer: Component files created
    Developer->>Component: Implement logic, view, styles
    Component-->>Developer: Standalone component ready

Loading

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 218e799 and 715c312.

Files selected for processing (1)

• docs/dev/guidelines/client.rst (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• docs/dev/guidelines/client.rst

---

Tip

Early Access Features

• gpt-4o model for chat

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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to full the review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @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.

[JohannesStoehr]

New documentation looks good to me

[pzdr7]

LGTM

[rabeatwork]

maintainer approve

[muradium]

LGTM