-
Notifications
You must be signed in to change notification settings - Fork 395
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
SearchQueryTool Feature Suggestion: Allow choice of nometadata for json #252
Comments
@GoonerW The tool itself as UI tool does not need it, and it's set to verbose to ensure backwards compatibility. It's also a bit of work to support parsing of two more payloads + crafting POST queries in minimal. What would the usecase be? |
I use the tool as an ad hoc query as I'm more of an admin that a developer (so manually crafting POST requests and the auth tokens is, while doable, not as easy). I just wanted to be able to copy the JSON produced and having the option of nometadata would be useful. If it's not a simple change to be able to accommodate the option then don't worry about it. I was more asking that if it was a trivial thing to add, it'd be nice. |
I thought about it a couple of years back, but didn't have a strong enough need at the time :) I'll keep it in mind. |
The tool defaults to metadata=verbose for its json output. Can we have an option to request minimal or nometadata?
The text was updated successfully, but these errors were encountered: