Skip to content

New internal extensions should no be treated as user extensions #14528

@cderv

Description

@cderv

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingextensionsrelates to Quarto extensions mechanism

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions