-
Notifications
You must be signed in to change notification settings - Fork 1
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
base: CHA-PR3h-etc
Are you sure you want to change the base?
Conversation
Mistake in 9c97883.
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.
Resolves #151.
I didn’t know the correct syntax ([1]). [1] https://www.swift.org/documentation/docc/linking-to-symbols-and-other-content#Navigate-to-a-Symbol
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).
Missed this in 1eb54c8.
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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
47fe83c
to
3e09520
Compare
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.
951e66b
to
cf769a1
Compare
Note: This PR is based on top of #163.
WIP for #1. What's here so far:
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.