| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
`all` kwarg is used to manage GitlabList generator behaviour. However, as it is not poped from kwargs, it is sent to Gitlab API. Some endpoints such as [the project commits](https://docs.gitlab.com/ee/api/commits.html#list-repository-commits) one, support a `all` attribute. This means a call like `project.commits.list(all=True, ref_name='master')` won't return all the master commits as one might expect but all the repository's commits. To prevent confusion, the same kwarg shouldn't be used for 2 distinct purposes. Moreover according to [the documentation](https://python-gitlab.readthedocs.io/en/stable/gl_objects/commits.html#examples), the `all` project commits API endpoint attribute doesn't seem supported.
|
Makes sense. To use the all parameter, you can supply it with query_parameters instead (starting with 1.8) |
Sorry, something went wrong.
|
@gpocentek We may need to update the documentation that all is not send to the GitLab API anymore by default. What do you think? |
Sorry, something went wrong.
|
@max-wittig yes, we need to add that info in the release notes |
Sorry, something went wrong.
|
@gpocentek Could you disable the travis requirement temporary to merge this? |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
all kwarg is used to manage GitlabList generator behaviour.
However, as it is not pop'ed from kwargs, it is sent to Gitlab API.
Some endpoints such as the project commits one,
support a all attribute.
This means a call like project.commits.list(all=True, ref_name='master')
won't return all the master commits as one might expect but all the
repository's commits.
To prevent confusion, the same kwarg shouldn't be used for 2 distinct
purposes.
Moreover according to the documentation,
the all project commits API endpoint attribute doesn't seem supported.