Repository navigation
Fix wasm SizeLimits OOM, talk TOC, and Roadmap cleanup #480
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
d27f071
Fix wasm-embedded OOM and refresh docs roadmap.
leogdion 2ed13c5
Keep only open Roadmap items; drop talk-article TOC.
leogdion 95fee1e
Remove Swift Rockies from talk venue listings.
leogdion 24d236f
Restore Table of Contents on the talk DocC article.
leogdion File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🤖 get_repo_knowledge executed:
get_repo_knowledge brightdigit/MistKit /tmp/coderabbit-repo-knowledge/brightdigit-mistkit-00afe656/conventionsLength of output: 17623
🏁 Script executed:
Repository: brightdigit/MistKit
Length of output: 26380
🌐 Web query:
SwiftDocC Identifier heading fragment capitalization anchor generated documentation💡 Result:
In SwiftDocC, documentation anchors for headings are generated by transforming the heading text into a standardized identifier format [1][2]. While exact implementation details can evolve, the following behaviors are standard for how SwiftDocC handles heading identifiers and fragment anchors: Capitalization: SwiftDocC generally normalizes generated URL fragments and certain identifiers to lowercase [3][4]. For example, render-side logic often utilizes "anchorize" functions that convert heading text to lowercase to ensure consistent behavior across different web server environments [4]. Anchor Generation: 1. When you use the doc:PageName#Heading-Title syntax to link to a heading, SwiftDocC automatically maps the heading title to an anchor identifier [5][1]. 2. The transformation process typically replaces whitespace characters with dashes (-) and may remove punctuation [5]. For instance, a heading titled "Example: Sloth's diet" can be referenced using an anchor like
#Example-Sloths-diet[5]. 3. SwiftDocC is designed to handle this transformation automatically; authors do not need to manually define the anchor ID [1][2]. Linking Best Practices: - To link to a heading on another page, use the syntax doc:PageName#Heading-Title [5][1]. - To link to a heading on the same page, you can use doc:`#Heading-Title` [6]. - If you find that a link is not resolving, ensure the heading level is supported (generally H2 and lower are automatically indexed as linkable anchor sections) [1][7]. - Because SwiftDocC manages the mapping of headings to URL fragments, it is recommended to use the title text directly in your links rather than attempting to guess a manually "slugified" ID, as the tool handles the translation [5][2]. Note that while symbol names are case-sensitive in Swift source code, the URL fragments and paths generated by SwiftDocC for navigation are intentionally lowercased to avoid cross-platform URL handling issues [3].Citations:
🏁 Script executed:
Repository: brightdigit/MistKit
Length of output: 11018
🌐 Web query:
site:swift.org/documentation/docc linking to headings same page DocC anchor case💡 Result:
To link to a heading on the same page in Swift DocC, you use the link syntax
<doc:HeadingName>. Including a hash prefix (#) before the heading name (e.g.,<doc:#HeadingName>) is also supported [1]. If the heading contains whitespace or punctuation, Swift DocC generates an anchor by replacing whitespace sequences with a dash and optionally removing punctuation [1]. Key considerations for linking to headings include: - Same-page vs. Cross-page: The syntax<doc:HeadingName>or<doc:#HeadingName>is used for the current page [1]. To link to a heading on a different page, use the syntax<doc:PageName#HeadingName>[1]. - Version History: Support for the leading hash (#) character in same-page links was introduced in Swift-DocC 5.9. Before that version, you must omit the hash for same-page links [1]. - Task Groups: Linking to task groups is supported as of Swift-DocC 6.0 [1]. - Resolution: If a task group is empty or its links fail to resolve, the task group is omitted from the rendered page, making it impossible to link to it [1]. Linking to generated per-symbol-kind task groups is not supported [1].Citations:
🏁 Script executed:
Repository: brightdigit/MistKit
Length of output: 19695
Use DocC-compatible section fragments.
DocC preserves heading capitalization when it normalizes fragments. Replace lowercase fragments such as
#overview,#what-is-cloudkit, and#whats-nextwith#Overview,#What-is-CloudKit, and#Whats-next. Apply the same change to every table-of-contents entry.🤖 Prompt for AI Agents
Source: MCP tools