Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ECO-4915] (WIP) Add documentation comments #165

Draft
wants to merge 22 commits into
base: CHA-PR3h-etc
Choose a base branch
from

Conversation

lawrence-forooghian
Copy link
Collaborator

@lawrence-forooghian lawrence-forooghian commented Nov 28, 2024

Note: This PR is based on top of #163.

WIP for #1. What's here so far:

  • fixes some existing documentation comments to make DocC happy
  • adds a CI job to run the DocC documentation compiler; this gives us checking of links to other symbols and a (rather overwhelming) documentation coverage report
  • Started copying across the documentation comments from the JS repo at 58a4fa2; the first few documentation comments are copied across with some light editing to match the Swift documentation syntax, but when it started to become clear that we were going to need deeper edits for a bunch of stuff I switched over to copying them over without any editing; we will have to do a second pass for editing. See commit messages for current progress.

This is in preparation for implementing CHA-PR3h, in which a given
numerical error code no longer necessarily implies a specific status
code (specifically, RoomInInvalidState may now have a 400 or 500 status
code depending on the context in which it is thrown).

The internal API introduced here is a bit convoluted and verbose, but
I’ve done it this way for two reasons:

1. It reflects the way the spec is written; most of the time a numeric
   code has a status code written alongside it

2. For the numerical error codes that _do_ always imply a certain status
   code, I want to be able to get that status code still, so that the
   existing Messages code that throws an error with the
   messagesAttachmentFailed code, as well as the isChatError(…) test
   helper, continue to work as they currently do.
I’m going to introduce the DocC documentation compiler, which fails to
resolve these links (there may well be a way to get it to do so, but I
won’t be looking into that now).
Copy link

coderabbitai bot commented Nov 28, 2024

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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
🪧 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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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 do a full 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.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

@lawrence-forooghian lawrence-forooghian changed the base branch from main to CHA-PR3h-etc November 28, 2024 19:16
Using the SwiftPM DocC Plugin because [1] describes it as the “preferred
option”.

Part of #1.

[1] https://www.swift.org/documentation/docc/documenting-a-swift-framework-or-package
Taken from JS repo at 58a4fa2, only edited to match Swift documentation
syntax.
Taken from JS repo at 58a4fa2, only edited to match Swift documentation
syntax.
Taken from JS repo at 58a4fa2, not edited at all.
Taken from JS repo at 58a4fa2, not edited at all.
Taken from JS repo at 58a4fa2, not edited at all.
Taken from JS repo at 58a4fa2, not edited at all.
Taken from JS repo at 58a4fa2, not edited at all.
Taken from JS repo at 58a4fa2, not edited at all.
Taken from JS repo at 58a4fa2, not edited at all.
Taken from JS repo at 58a4fa2, not edited at all.
Taken from JS repo at 58a4fa2, not edited at all.
Taken from JS repo at 58a4fa2, not edited at all.
Taken from JS repo at 58a4fa2, not edited at all.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant