Merge lp:~bryce/launchpad/api-doc-fixes into lp:launchpad
Proposed by
Bryce Harrington
Status: | Merged |
---|---|
Approved by: | Bryce Harrington |
Approved revision: | no longer in the source branch. |
Merged at revision: | 10882 |
Proposed branch: | lp:~bryce/launchpad/api-doc-fixes |
Merge into: | lp:launchpad |
Diff against target: |
122 lines (+36/-12) 2 files modified
lib/lp/bugs/interfaces/bugtarget.py (+3/-3) lib/lp/bugs/interfaces/bugtask.py (+33/-9) |
To merge this branch: | bzr merge lp:~bryce/launchpad/api-doc-fixes |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Abel Deuring (community) | code | Approve | |
Review via email: mp+24786@code.launchpad.net |
Commit message
Improve the bugtask searchTask() parameter documentation, to clarify some items and fill in stub text.
Description of the change
This fills in stub docs for some of the bugtask search fields and makes them a bit more consistent with other api documentation.
To post a comment you must log in.
Hi Bryce,
thanks for improving and cleaning up the docs!
I have mostly formal nitpicks: "make lint" says that several lines are too long:
lib/lp/ bugs/interfaces /bugtask. py
780: [C0301] Line too long (87/78)
789: [C0301] Line too long (90/78)
822: [C0301] Line too long (97/78)
827: [C0301] Line too long (190/78)
834: [C0301] Line too long (90/78)
842: [C0301] Line too long (87/78)
864: [C0301] Line too long (136/78)
Could you break the string up so that the line length does not exceed 78 characters? Our typical style looks like this:
status = List(
title= _('Status' ),
description= _(
value_ type=Choice(
title= _('Status' ),
vocabulary =BugTaskStatusS earch,
default= BugTaskStatusSe arch.NEW) ,
default= list(DEFAULT_ SEARCH_ BUGTASK_ STATUSES) ,
required= False)
title= _('Importance' ),
description= _(
'importanc es.'),
value_ type=IBugTask[ 'importance' ],
required= False)
'Show only bugs with the given status value or list of values.'),
importance = List(
'Show only bugs with the given importance or list of '
> @@ -800,7 +806,7 @@
> statusexplanation = TextLine(
> title=_("Status notes"), required=False)
> has_patch = Bool(
> - title=_('Show only bugs with patches available'), required=False,
> + title=_('Show only bugs with patch attachments.'), required=False,
> default=False)
I am not sure if we should combine the words "patch" and "attachment" in this context: A bug page has two portlets called "patches" and "bug attachments", thus distiguishing between patches and other|ordinary| regular attachments. Naive users might be confused by the term "patch attachment": does it means only patches, or does it mean patches aand/or other attchments? I would prefer to keep the old text to avoid this possible confusion. Alternatively, we could change the text in the portlets to "patch attachments" and "non-patch attachments" or "other attachments" or similar for the sake of consistency and to make the distinction between patches and other attachments more obvious.