posit-dev / posit-dev/rsconnect-python

write-manifest quarto doesn't support Shiny Quarto documents

Open
#754 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
37
Forks
28
Avg merge
1d 3h
Merged PRs (30d)
7

Description

Summary

rsconnect write-manifest quarto always creates a static document manifest, even for Quarto documents that use server: shiny in their YAML front matter. There's no way to generate a quarto-shiny manifest via the CLI.

Details

The codebase has support for AppModes.SHINY_QUARTO internally, but the CLI doesn't expose this functionality:

  • No --shiny flag on write-manifest quarto
  • No auto-detection of server: shiny in the Quarto document's YAML front matter
  • write-manifest shiny doesn't recognize .qmd files as valid entry points

Current workarounds

  1. Use quarto publish connect instead (which does handle this correctly)
  2. Manually create a manifest.json with "appmode": "quarto-shiny"

Expected behavior

Either:

  • write-manifest quarto should detect server: shiny in the document and create a quarto-shiny manifest automatically, OR
  • A --shiny flag should be added to explicitly request a Shiny Quarto manifest

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the write-manifest quarto and write-manifest shiny CLI entry points, then trace the existing AppModes.SHINY_QUARTO support. Check how Quarto YAML front matter and valid entry points are handled. Done means the CLI can produce a quarto-shiny manifest for a .qmd document using server: shiny, either through detection or an explicit flag.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.