什么时候会有 API Reference？最起码给个 Auto Generated 的 Reference Doc？

Open
#103 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api, documentation

Research direction

The issue names no files, tests, or documentation tooling. Start by locating the SDK's public API entry points and any existing documentation-generation setup; clarify the expected reference format and scope before implementing anything. Done means the agreed API reference is generated and published with the project.

Written by the indexing model from the issue text.

Description

This issue has no description.

Dominant language
Python
Stars
559
Forks
102
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from larksuite/oapi-sdk-python

All issues in larksuite/oapi-sdk-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.