Skip to content

Commit

Permalink
Fix typos in JIRA's default_batch_sizes docstring
Browse files Browse the repository at this point in the history
___
Jannik Meinecke (<jannik.meinecke@mercedes-benz.com>) on behalf of MBition GmbH.
[Provider Information](https://github.com/mercedes-benz/foss/blob/master/PROVIDER_INFORMATION.md)
  • Loading branch information
rynkk committed Jun 10, 2022
1 parent c40b32c commit cf8014f
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions jira/client.py
Original file line number Diff line number Diff line change
Expand Up @@ -474,9 +474,9 @@ def __init__(
logging (bool): Determine whether or not logging should be enabled. (Default: True)
default_batch_sizes (Optional[Dict[Type[Resource], Optional[int]]]): Manually specify the batch-sizes for
the paginated retrieval of different item types. `Resource` is used as a fallback for every item type not
specified. If a item type is mapped to `None` no fallback occurs, instead the JIRA-Backend will use its
specified. If an item type is mapped to `None` no fallback occurs, instead the JIRA-backend will use its
default batch-size. By default all Resources will be queried in batches of 100. E.g., setting this to
``{Issue: 500, Resources: None}`` will make :py:meth:`search_issues` query Issues in batches of 500, while
``{Issue: 500, Resource: None}`` will make :py:meth:`search_issues` query Issues in batches of 500, while
every other item type's batch-size will be controlled by the backend. (Default: None)
"""
Expand Down

0 comments on commit cf8014f

Please sign in to comment.