You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to #1210, let's add pagination support for buildtest history command via --pager and -p option.
Let's remove the -p option from buildtest history list and move this up a level to buildtest history --pager
(buildtest) ~/Documents/github/buildtest/ [update_buildtest_help+*] buildtest history list -h
usage: buildtest [options] [COMMANDS] history list [-h] [-n] [-t] [--pager]
optional arguments:
-h, --help show this help message and exit
-n, --no-header Do not print header columns in terse output (--terse)
-t, --terse Print output in machine readable format
--pager Enabling PAGING when viewing result
We should have buildtest history --pager list work exactly how buildtest history list --pager works.
The pagination for buildtest history query should work in the following cases
Please describe your feature request
Similar to #1210, let's add pagination support for buildtest history command via
--pager
and-p
option.Let's remove the
-p
option frombuildtest history list
and move this up a level tobuildtest history --pager
We should have
buildtest history --pager list
work exactly howbuildtest history list --pager
works.The pagination for
buildtest history query
should work in the following casesbuildtest history -p query 0
buildtest history -p query 0 --output
Action Item
--pager
and-p
option in https://github.com/buildtesters/buildtest/blob/devel/buildtest/cli/__init__.py and also remove this frombuildtest history list --pager
.buildtest history list
andbuildtest history query <id>
. https://github.com/buildtesters/buildtest/blob/devel/buildtest/cli/history.pybuildtest history list --pager
option is removed from bash completionbuildtest help history
pertaining to pagination in https://github.com/buildtesters/buildtest/blob/devel/buildtest/cli/help.pyPost question in Slack
Is there an existing issue
The text was updated successfully, but these errors were encountered: