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 a --format and a --json option to the search command #89

Closed
wants to merge 16 commits into from

Conversation

talwrii
Copy link
Contributor

@talwrii talwrii commented Aug 26, 2015

The --json options makes it easier to use search results programmatically. It also acts as documentation for --format.

--format is quite useful for ad hoc querying (e.g - how many bugs does each project have, how many bugs are there of this priority etc etc)

jbeich and others added 16 commits August 1, 2015 07:32
Quoting uses percent encoding and the `%` symbol itself must be quoted
with extra `%` for configparser.
Useful for programmtic usage and discovering field for format
Has --json and --format argument like search
With --json and --format arguments
Lists all the components and their products
Conflicts:
	bugz/argparser.py
	bugz/cli.py
This is not by manually searching the bugs.
This also allows empty searches... occassionally
listing all the bugs is useful
command to reset a bug to its default owner
@williamh
Copy link
Owner

williamh commented Feb 8, 2016

This pull request has far too many unrelated features for me to review.
A pull request should contain commits related to one feature only and should be on a topic branch instead of master.

I'm very interested in this code, but I need it in small pull requests so that I can review and merge them more easily.

Thanks,

William

@williamh williamh closed this Feb 8, 2016
@talwrii
Copy link
Contributor Author

talwrii commented Feb 9, 2016

Aha, yes. I issued a pull request from master a few months ago, forgot about the merge request, and kept on adding stuff. I shall split this into a few topic branches for you. It was about one thing when I made it :P .

If I recall correctly, there were also some file renames and whitespace changes that I merged in...

That being said most of my pull requests are probably going to consist of one patch :)

@talwrii
Copy link
Contributor Author

talwrii commented Feb 9, 2016

Pull requests:

--format and --json options for search: #92
--unassign option on modify: #93
product and component commands: #94
my preferences for bugz get (contentious): #95
not-status search option and allow (contentious) open search: #96

Okay I've run out of steam now. I still have patches for

  1. Ordering of comments
  2. Sorting of bugs

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

3 participants