Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Format' support for search() (format' parameter of Ticket Search) #17

Merged
merged 1 commit into from Jun 25, 2018
Merged

Add Format' support for search() (format' parameter of Ticket Search) #17

merged 1 commit into from Jun 25, 2018

Conversation

iamleot
Copy link
Contributor

@iamleot iamleot commented Jun 23, 2018

Previously when doing a search() the format was always l (all
possible fields were returned). It can be often handy to limit the
fields returned and RT permits to also have i and s format
search.

Add a Format argument to search() (by default l) in order to
permit to inject the corresponding format field in the search
HTTP request.

For more information regarding the format parameter of Ticket Search please
give a look to:

https://rt-wiki.bestpractical.com/wiki/REST#Ticket_Search

If only ticket id and/or id and subject are needed passing Format=i
or Format=s speed up the reply of a search a lot.

Previously when doing a search() the format was always `l' (all
possible fields were returned). It can be often handy to limit the
fields returned and RT permits to also have `i' and `s' format
search.

Add a `Format' argument to search() (by default `l') in order to
permit to inject the corresponding `format' field in the search
HTTP request.
@e3rd e3rd merged commit 48fd94a into python-rt:master Jun 25, 2018
@e3rd
Copy link
Collaborator

e3rd commented Jun 25, 2018

Seems good, thanks!

@iamleot
Copy link
Contributor Author

iamleot commented Jun 25, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants