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

hpi query improvement ideas #318

Open
seanbreckenridge opened this issue Oct 6, 2023 · 1 comment
Open

hpi query improvement ideas #318

seanbreckenridge opened this issue Oct 6, 2023 · 1 comment

Comments

@seanbreckenridge
Copy link
Contributor

seanbreckenridge commented Oct 6, 2023

sort of a follow up to https://memex.zulipchat.com/#narrow/stream/279601-hpi/topic/new.20HPI.20query.2Fserialization.20feature/near/270313599

To just track common patterns I see myself using with hpi query, so they could possibly be moved into python instead of in the shell using jq

I will probably work on adding some of these, just wanted to track the ideas first

dont want to necessarily just add every possible jq-like query/map/filter function, but these are the ones I find myself doing very often. Probably better to leave more complex operations to jq or something else

@karlicoss
Copy link
Owner

Another thing I often wanted -- often during debugging/testing it's useful to restrict the get_files call to one or a few input files.
Currently I am just editing the source directly but might be nice if it was somehow possible to pass it to hpi query, e.g. hpi query --inputs '[path1, path2, path3]' modulename....
Not sure how to do that reliably and consistently, I feel like it's going to be hacky either way. But in the first approximation it could monkey patch get_inputs function for modulename?

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

No branches or pull requests

2 participants