Skip to content

Conversation

cscheid
Copy link
Collaborator

@cscheid cscheid commented Aug 1, 2025

executable code cells can then access relevant information by loading the JSON file and reading fields as needed.

@posit-snyk-bot
Copy link
Collaborator

posit-snyk-bot commented Aug 1, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

@cscheid cscheid marked this pull request as ready for review August 4, 2025 13:24
@cscheid cscheid merged commit afa839e into main Aug 4, 2025
122 of 135 checks passed
@cscheid cscheid deleted the feature/quarto-execute-info-env branch August 4, 2025 20:57
@cderv
Copy link
Collaborator

cderv commented Aug 25, 2025

Do you agree we should document QUARTO_EXECUTE_INFO content now that we expose it all?

As we are deferring to users to retrieve the information they need instead of providing them directly pieces of it.

I believe QUARTO_EXECUTE_INFO should be added https://prerelease.quarto.org/docs/advanced/environment-vars.html#variables-quarto-sets and there in the table we could link to another doc that gives information on each field that could be in QUARTO_EXECUTE_INFO.

Also, I plan to provide scoped helpers to retrieve some of the information more easily, depending on the use case, in the Quarto R package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants