Support the Quarto knitr engine when deploying content

Open Beginner friendly
#786 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
python, r
Domain
cli

Research direction

Start in rsconnect/actions.py at validate_quarto_engines to trace the current engine validation, then inspect the four Quarto entry points in rsconnect/main.py and their existing jupyter and markdown branches. Confirm deployment works for Quarto content using knitr, including manifest writing and the no-Python-environment case, using the existing entry points and related checks as guidance.

Written by the indexing model from the issue text.

Description

Goal

Allow content using the Quarto knitr engine to be deployed and to have a
manifest written. Today validate_quarto_engines (rsconnect/actions.py) accepts
only markdown and jupyter and rejects everything else, including knitr.

Why

knitr is the default Quarto engine for documents that mix R and Python chunks.
Now that rsconnect-python can carry R dependencies from renv.lock, the original
reason for excluding knitr no longer applies, so the rejection blocks a case
the tool can otherwise handle. Raised in review:
https://github.com/posit-dev/rsconnect-python/pull/785#discussion_r3431999679

References

  • rsconnect/actions.py (validate_quarto_engines) — the engine allowlist.
  • rsconnect/main.py — the four Quarto entry points already branch on
    "jupyter" in engines and handle the no-Python-environment case (markdown).
  • renv.lock R-dependency support: PR: support for parsing renv.lock #785
Dominant language
Python
Stars
37
Forks
28
Avg merge
1d 3h
Merged PRs (30d)
7

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.

More from posit-dev/rsconnect-python

All issues in posit-dev/rsconnect-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.