posit-dev / posit-dev/connectapi
`Content$update()` should use the response of the `PATCH` to replace the `Content` object's local data.
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 54
- Forks
- 27
- Avg merge
- 1d 3m
- Merged PRs (30d)
- 1
Description
The Content$update() method of the Content class updates content on the server but does not update the local copy of the data, requiring another call to do so or simply working with an out-of-sync piece of content.
Any code calling Content$update() internally should be audited — if it calls Content$get_content_remote() after that call can be removed.
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 Content$update() and audit any internal callers that invoke Content$get_content_remote() afterward. Confirm that the local Content data reflects the PATCH response and that redundant remote fetches are removed where appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100