Skip to content

Conversation

@robtaylor
Copy link
Contributor

Summary

  • Make all attribute descriptions in IOModelOptions use consistent multi-line formatting
  • This fixes RST definition list parsing issues when building docs with sphinx-autoapi

Notes

The remaining warnings in chipflow-docs related to this repo are:

  1. Config module warnings: These come from inherited pydantic BaseModel docstrings which use Markdown syntax. These can't be fixed in chipflow-lib - they would need to be suppressed in the docs build or addressed upstream in pydantic.
  2. Ambiguous Interface cross-reference warnings: These occur because multiple classes share the same name (e.g., amaranth_soc.csr.bus.Interface, amaranth.lib.stream.Interface). These can be fixed by using fully-qualified names in docstrings or suppressing them in Sphinx config.

Test plan

  • Build chipflow-docs with warning suppression disabled and verify the IOModelOptions definition list warnings are resolved

🤖 Generated with Claude Code

@github-actions
Copy link

github-actions bot commented Dec 17, 2025

PR Preview Action v1.6.3
Preview removed because the pull request was closed.
2025-12-17 20:36 UTC

@github-actions
Copy link

github-actions bot commented Dec 17, 2025

Tests Skipped Failures Errors Time
68 4 💤 0 ❌ 0 🔥 23.612s ⏱️

- Make all attribute descriptions in IOModelOptions use consistent multi-line
  formatting to avoid RST definition list parsing issues
- Add docstrings to config model classes that were missing them, preventing
  inherited pydantic BaseModel docstrings (which use Markdown syntax) from
  being displayed

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@robtaylor robtaylor force-pushed the fix/docstring-warnings branch from 082f17d to 03c8dbb Compare December 17, 2025 20:09
@robtaylor robtaylor merged commit 1627522 into main Dec 17, 2025
6 checks passed
@robtaylor robtaylor deleted the fix/docstring-warnings branch December 17, 2025 20:34
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