Skip to content

Behavior of quarto_create_project() differs from quarto create-project since the former "requires" the creation of a new directory #148

Open
@davidkane9

Description

@davidkane9

I am used to creating the framework for a Quarto website by running, from the Terminal, this command:

quarto create-project "." --type website

This just dumps the required files into the current directory. I had hoped that, from the R Console, this command:

quarto_create_project(type = "website")

would behave the same. But, it fails because, as documented, you need to supply a "name" argument, which becomes a newly created directory in which the required files are placed.

I think that the behavior of quarto_create_project() should be more similar to the behavior of quarto create-project by default. At the least, it should be possible to somehow use quarto_create_project() to produce the required files in the current directory, without creating a new directory.

I was able to accomplish this by running:

quarto_create_project(name = ".", type = "website")

That works. But should it?

Metadata

Metadata

Assignees

No one assigned

    Labels

    upstreamconcerns an upstream library like quarto or pandoc

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions