Proof-of-concept implementation of CLI list command #3273
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I support this. Thanks for working on it 🙏 Ideally:
An other command to add would be |
|
Was there a reason this was closed? Can this get re-opened? I find myself needing this again. I rebased this PR on the latest master, and I've done a bit of cleanup. For my current use-case I want to add the ability for users to specify a few more information columns, which I don't think will be difficult. I've added initial logic for a json machine readable output, but it needs a bit of work. I have a backup of the original PR here: https://github.com/Erotemic/girder/tree/dev/cli_list_old |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There have been a few times where I've wished I could use the CLI to list or describe the data in a folder / collection / item / file.
I have a basic implementation of this feature. It works well enough, but it could be better.
I''ve currently tested with the following commands to list items in the VIAME girder collection:
This results in the following output:
It would be nice to harden up this CLI, or even make it easier to implement on the CLI side. It would be nice to have a query-by-name feature, so you could traverse girder in a similar way that you would traverse a file system. It would also be nice to list extra column information like sha512 hashes if they exist.
There are probably a lot of directions you could go with this, but I think the girder-cli is lacking in that it has no way to query what data exists. So this is an attempt to fix that.