posit-dev / posit-dev/connect-extensions
Polish publisher-command-center
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 10
- Forks
- 8
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 1
Description
Baselines:
- Rewrite README (currently 13 lines): what it does, who it's for, setup/config, how to use
- Rewrite description: concise, states functionality + value
- Add a "how this works" panel: surface the Visitor API Key identity mechanism ("acting as {you}; you see only the content you can manage")
- Add why-comments to the source
App-specific:
- Add backend test suite + CI
- Add frontend (Mithril) test suite + CI
- Fix N+1 in GET /api/contents
- Fix dead async error handling across components
- Guard null-date formatting crashes
- Return proper HTTP errors instead of raw 500s
- Delete or fix the broken Metrics feature; remove stray console.logs
- Bump version, CHANGELOG, checksums
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 by inventorying the README, backend and Mithril frontend entry points, the GET /api/contents handler, components, and Metrics feature. Check the existing test and CI setup first. Done means the documentation, tests, CI, error handling, performance, Metrics, logging, and release checklist items are all addressed and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, r
- Domain
- backend-api-design, ci-cd, documentation, full-stack, performance, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100