Skip to content

docs(rust): API reference master #80

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.

Sign up for GitHub

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
WomB0ComB0 merged 1 commit into from
May 15, 2026
Merged

docs(rust): API reference master #80

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2554,4 +2554,4 @@
"website": "https://resq.software"
}
}
}
}
1 change: 0 additions & 1 deletion sdks/rust/api/resq-bin/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -376,5 +376,4 @@ Licensed under the Apache License, Version 2.0. See [LICENSE](http://www.apache.
Click through to each module for the full rustdoc-rendered API surface (types, traits, functions, methods).

- [`analysis`](./analysis)
- [`bin_explorer`](./bin_explorer)
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot May 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The removal of the bin_explorer module link here creates an inconsistency with docs.json (line 2169) and sdks/rust/api/_pages.json (line 7). Per repository rules, documentation lists must remain consistent with source-of-truth configuration files. Furthermore, ensure these changes are applied to the source-level documentation (e.g., XML doc comments) or the configuration files themselves, rather than manually editing generated files, to ensure the changes persist across regeneration cycles.

References
  1. When maintaining lists in auto-generated documentation, ensure the generator logic enforces consistent ordering to match source-of-truth configuration files like _pages.json.
  2. When fixing errors in auto-generated documentation, apply the changes to the source-level documentation instead of the generated files to ensure the fixes persist across regeneration cycles.


Loading