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

feat(docs): publish documentation #149

Merged
merged 1 commit into from
Mar 11, 2025
Merged

Conversation

TimMenninger
Copy link
Contributor

@TimMenninger TimMenninger commented Mar 11, 2025

Creates an api_reference.rst file to expose the existing documentation for the few functions that have docstrings, as well as add documentation for AddrInfoType and SocketFactoryType. Now, these can be properly pointed to by other projects' documentation.

What do these changes do?

Publish documentation so it can be pointed to by other projects.

Are there changes in behavior for the user?

No.

Related issue number

N/A

Checklist

  • I think the code is well written
  • Unit tests for the changes exist
  • Documentation reflects the changes

Creates an api_reference.rst file to expose the existing documentation
for the few functions that have docstrings, as well as add documentation
for AddrInfoType and SocketFactoryType. Now, these can be properly
pointed to by other projects' documentation.
Copy link

codecov bot commented Mar 11, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (17d5e48) to head (1e3e784).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #149   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            5         5           
  Lines          250       250           
  Branches        53        53           
=========================================
  Hits           250       250           

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

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@TimMenninger TimMenninger marked this pull request as ready for review March 11, 2025 00:45
@bdraco
Copy link
Member

bdraco commented Mar 11, 2025

Thanks. Traveling this week. I'll take a look when I get back home and at my desk

@bdraco bdraco closed this Mar 11, 2025
@bdraco bdraco reopened this Mar 11, 2025
@bdraco
Copy link
Member

bdraco commented Mar 11, 2025

close/reopen to re-run CI

Copy link
Member

@bdraco bdraco left a comment

Choose a reason for hiding this comment

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

Thanks @TimMenninger

@bdraco
Copy link
Member

bdraco commented Mar 11, 2025

I fixed the RTD build so a preview can be seen here https://aiohappyeyeballs--149.org.readthedocs.build/en/149/

@TimMenninger TimMenninger force-pushed the update-docs branch 2 times, most recently from 1e3e784 to 67f710f Compare March 11, 2025 17:04
@bdraco bdraco changed the title docs: publish documentation feat(docs): publish documentation Mar 11, 2025
@bdraco bdraco merged commit 4235273 into aio-libs:main Mar 11, 2025
61 of 64 checks passed
@bdraco
Copy link
Member

bdraco commented Mar 11, 2025

Thanks @TimMenninger

@webknjaz
Copy link
Member

FWIW, the generated document is typically gitignored with such extensions.

@bdraco
Copy link
Member

bdraco commented Mar 12, 2025

FWIW, the generated document is typically gitignored with such extensions.

I'm not following. Are you suggesting to ignore ./_build/html/api_reference.html and ./_build/doctrees/api_reference.doctree AFAICT everything in _build should already be ignored

docs/_build/
?

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.

3 participants