Skip to content

Summary API Docs#307

Merged
rwb27 merged 4 commits intomainfrom
summary_api_docs
Apr 2, 2026
Merged

Summary API Docs#307
rwb27 merged 4 commits intomainfrom
summary_api_docs

Conversation

@rwb27
Copy link
Copy Markdown
Collaborator

@rwb27 rwb27 commented Apr 1, 2026

This is an attempt to improve the user-facing documentation. Rather than the previous somewhat awkward approach of making the various symbols that are promoted to lt.* disappear from the modules they're actually defined in, then showing them at the top level, this PR creates a new "quick reference API documentation" page with summaries of the key classes/functions.

These summary definitions may be referenced with lt.Thing or lt.property. This serves two purposes:

  1. It keeps people out of the full autogenerated API docs unless they need to be there.
  2. It means the docs can reflect the syntax we actually want people to use (e.g. @lt.action for the decorator).

I think the new quick reference page is going to be quite useful, but I think it's worth taking suggestions on this structure...

@rwb27 rwb27 changed the title Include the "description" of the Thing in the thing_description Summary API Docs Apr 1, 2026
@rwb27 rwb27 marked this pull request as draft April 1, 2026 21:54
@rwb27 rwb27 force-pushed the summary_api_docs branch from ac41048 to 9d7e3da Compare April 2, 2026 11:37
@rwb27 rwb27 marked this pull request as ready for review April 2, 2026 12:29
@rwb27 rwb27 modified the milestone: v0.2.0 Apr 2, 2026
Copy link
Copy Markdown
Contributor

@julianstirling julianstirling left a comment

Choose a reason for hiding this comment

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

My only worry I think here is how we make sure the full signatures in the public API file are always correct in full? A checkbox helps, but it feels like a bit of stop-gap?

rwb27 added 3 commits April 2, 2026 16:01
This builds the docs in CI, and then checks the `lt` symbols against our top-level `__all__`. Hopefully, doing so will stop things getting out of date.
FEATURE_FLAGS is an object not a class, which confuses my code that deduplicates re-exported symbols.

I have added FEATURE_FLAGS as a special case.
@rwb27 rwb27 force-pushed the summary_api_docs branch from 56c1fe3 to ec4e4d6 Compare April 2, 2026 15:01
This adds in the remaining symbols and renames "quick reference" to "public API".

Renaming the full API docs required me to pull in templates for autoapi. This might go away in the future if we transition fully to autodoc.

I've had to fix a couple of references too.
@rwb27 rwb27 force-pushed the summary_api_docs branch from ec4e4d6 to 079566f Compare April 2, 2026 15:26
@rwb27
Copy link
Copy Markdown
Collaborator Author

rwb27 commented Apr 2, 2026

I've made an issue to set up a merge checklist. I think there might be some scope for more automation here too, but it will require a bit of thought to get right.

@rwb27 rwb27 merged commit ab6b0c6 into main Apr 2, 2026
15 checks passed
@rwb27 rwb27 deleted the summary_api_docs branch April 2, 2026 15:29
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