Add missing API documentation for all exported symbols #3887
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.
Summary
This PR ensures all public API elements in ModelingToolkit.jl are properly documented. After analyzing all 270 exported symbols, I identified several categories of functions that were not included in the documentation and added appropriate documentation files and sections.
Changes
New Documentation Files Created
docs/src/API/structural_transformation.md
- Documents structural transformation functions including:tearing
,tearing_reassemble
, etc.)dae_index_lowering
,pantelides\!
, etc.)check_consistency
)sorted_incidence_matrix
,but_ordered_incidence
)docs/src/API/bipartite_graph.md
- Documents bipartite graph functionality including:BipartiteGraph
,BipartiteEdge
,DiCMOBiGraph
,DiffGraph
)𝑠vertices
,𝑑vertices
, etc.)maximal_matching
,construct_augmenting_path\!
)equation_dependencies
,variable_dependencies
, etc.)asgraph
,asdigraph
)Updated Documentation Files
docs/src/API/System.md
- Added missing sections for:LinearizationProblem
,get_sensitivity_function
, etc.)docs/pages.jl
- Updated to include the new documentation files in the API sectionCoverage Achieved
@docs
macro to automatically pull docstrings from the source codeTesting
The documentation structure has been verified to include all exported symbols. The actual docstrings will be populated when the documentation is built, pulling from the source code where these functions are defined.
🤖 Generated with Claude Code
Co-Authored-By: Claude [email protected]