posit-dev / posit-dev/connect-extensions
Polish chat-with-content
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 10
- Forks
- 8
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 1
Description
Potential changes (non-exhaustive list):
- Rewrite README into a genuinely useful doc: what it does, who it's for, setup/config, how to use
- Rewrite description: concise, states functionality + value
- Add a "how this works" surface: show the mechanism in-app (e.g. "signed in as {you}, resolved from your session; content read with your permissions, no admin key stored")
- Add why-comments to the source
- Add test suite + CI (none today)
- Make the startup Bedrock credential probe conditional
- Guard against undefined chat / null dates
- Truncate page DOM before sending to the LLM
- Surface real chat errors (on_error="actual")
- Refresh dated model names; drop duplicate chatlas pin
- 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 with the README and the chat-with-content entry point, then inventory the requested documentation, error handling, credential, DOM, model, and release changes before narrowing the scope. Treat the proposed test suite and CI, CHANGELOG, and checksums as validation and release work. Done should mean an agreed subset is implemented and documented with coverage for the selected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, r
- Domain
- backend, ci-cd, documentation, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100