Merge lp:~jtv/maas/extract-doc-handler into lp:~maas-committers/maas/trunk
Status: | Merged |
---|---|
Approved by: | Jeroen T. Vermeulen |
Approved revision: | no longer in the source branch. |
Merged at revision: | 2744 |
Proposed branch: | lp:~jtv/maas/extract-doc-handler |
Merge into: | lp:~maas-committers/maas/trunk |
Diff against target: |
499 lines (+210/-194) 5 files modified
src/maasserver/api/api.py (+2/-190) src/maasserver/api/doc_handler.py (+202/-0) src/maasserver/api/tests/test_describe.py (+1/-1) src/maasserver/management/commands/generate_api_doc.py (+1/-1) src/maasserver/urls_api.py (+4/-2) |
To merge this branch: | bzr merge lp:~jtv/maas/extract-doc-handler |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jeroen T. Vermeulen (community) | Approve | ||
Review via email: mp+231179@code.launchpad.net |
Commit message
Extract API handler: documentation.
Description of the change
This isn't quite like the other handlers. But extracting this is still worth the bother because in the end, we'll be able to "extract" the last big chunk (nodes, presumably) by renaming api.py to match its last remaining handlers. And at least for that last big chunk, revision history and pending changes will be unaffected.
We can do better with the doc and doc_handler modules: the docstring that is used as the top matter for the generated API documentation is now in doc_handler.py, which is a bit weird. Good ideas and motivation for cleaning things up further are welcome. I'm doing this not just to make the codebase nicer but to make it easier for others to improve it further!
Jeroen
Looks OK. Self-approving.