Test rust docs in rust #112
Merged
Conversation
This file contains 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
sstanfield
approved these changes
Jan 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
made a test that checks the format of rust docs, or at least, the strings the get-prop function gets for the :doc-string keywork
migrated some docs over from sl-sh
added some EXEMPTIONS
did a bit of work with the ErrorStrings I'm basing my errors in the conversion lib functions.
main point was to get the docstrings in rust and make sure they were formatted correctly so if you break something in rust, cargo test tells you. obviously incomplete because of the EXEMPTIONS set but it is a start. Mainly a pre-cursor to me actually eval-ing the Example: sections for the docs that do have them.