CLI UX improvement: `dsc extension list`
Open
Nobody has claimed this yet.
Issue-Enhancement
Up-for-Grabs
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Summary of the new feature / enhancement
As a user, I want to quickly filter for available extensions by their metadata,
so that I can search for relevant extensions when I don't know their name
without having to retrieve all extensions and filter with a pipeline.
Proposed technical implementation details (optional)
We could add support for the following filtering options:
--version, accepting a semantic version requirement--capabilities, accepting a literal capability. Users can specify multiple times to create and AND filter, sodsc extension list --capability discover --capability secretwould only return extensions with both thediscoverandsecretcapabilities.--description, accepting a string with wildcards that matches on the text of that field.--author, accepting a string with wildcards that matches on the text of that field.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the implementation and tests for the dsc extension list command, then inspect how extension metadata is represented and currently displayed. Done means the command supports semantic-version, capability, description-wildcard, and author-wildcard filters, including repeated capability filters that are ANDed together.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100