posit-dev / posit-dev/connectapi
Add object describing user-facing app mode groups
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 54
- Forks
- 27
- Avg merge
- 1d 3m
- Merged PRs (30d)
- 1
Description
Various Connect Gallery content use groupings of app modes that are taken from Connect's content list field. It would be good to move that data into connectapi. Perhaps it also belongs in Connect's API somewhere. (e.g. https://github.com/posit-dev/connect-extensions/pull/164#discussion_r2132204084)
app_mode_groups <- list(
"API" = c("api", "python-fastapi", "python-api", "tensorflow-saved-model"),
"Application" = c(
"shiny",
"python-shiny",
"python-dash",
"python-gradio",
"python-streamlit",
"python-bokeh"
),
"Jupyter" = c("jupyter-static", "jupyter-voila"),
"Quarto" = c("quarto-shiny", "quarto-static"),
"R Markdown" = c("rmd-shiny", "rmd-static"),
"Pin" = c("pin"),
"Other" = c("unknown")
)
app_mode_lookup <- with(
stack(app_mode_groups),
setNames(as.character(ind), values)
)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the connectapi package by locating how Connect content list fields and app modes are represented. Compare the proposed app_mode_groups and app_mode_lookup with the existing API model and the referenced Connect API discussion; done means the grouping data has a clear, usable home in connectapi or an explicitly identified Connect API location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100