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

Fix several rustdoc warnings #271

Merged
merged 1 commit into from
Sep 6, 2024

Conversation

FreezyLemon
Copy link
Contributor

See cargo doc for the warnings. Just some trivial things, like URLs broken across multiple lines and empty code blocks.

Copy link

codecov bot commented Sep 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.54%. Comparing base (f7689fc) to head (b3a4381).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #271      +/-   ##
==========================================
- Coverage   93.54%   93.54%   -0.01%     
==========================================
  Files          53       53              
  Lines       11662    11657       -5     
==========================================
- Hits        10909    10904       -5     
  Misses        753      753              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@YeungOnion YeungOnion left a comment

Choose a reason for hiding this comment

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

References can italicize with markdown underscore instead of HTML considering we use backticks for code.

All else is good, thanks again!

@YeungOnion YeungOnion merged commit d0a5b04 into statrs-dev:master Sep 6, 2024
8 checks passed
@FreezyLemon FreezyLemon deleted the fix-rustdoc-warnings branch September 6, 2024 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants