quarto-dev / quarto-dev/quarto-cli
New internal extensions should no be treated as user extensions
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
I think this is not just about showing info... this is the whole design for those internal extension that probably need to be adapted - internal extensions can't behave like user ones.
Otherwise, you can do this
❯ quarto list extensions
Id Version Contributes
julia-engine 0.1.0
orange-book 0.1.0 formats
❯ quarto remove orange-book
? Are you sure you'd like to remove Typst Orange Book Format? (Y/n) » Yes
Extension removed.
❯ quarto list extensions
Id Version Contributes
julia-engine 0.1.0
And this remove file in the installation directory of quarto
❯ ls -a C:\Users\chris\scoop\apps\quarto-prerelease\current\share\extension-subtrees\orange-book\
.gitignore LICENSE README.md
Leading to broken state... 😞
Originally posted by @cderv in #14527
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 tracing the extension handling behind quarto list extensions and quarto remove orange-book, then inspect how the installation directory's share/extension-subtrees/orange-book/ is affected. Done means internal extensions are not treated as removable user extensions and removing a user extension cannot leave the installation in a broken state.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100