posit-dev / posit-dev/connectapi
Consider removing warnings from unversioned / experimental APIs
Open
Nobody has claimed this yet.
size:sm
ux
- Dominant language
- R
- Stars
- 54
- Forks
- 27
- Avg merge
- 1d 3m
- Merged PRs (30d)
- 1
Description
Implementing a supported content_render() method using the experimental APIs causes warnings. During a discussion on that PR, it was suggested that we just remove the "unsupported API warnings", as they're probably just noise that everyone ignores.
See here for discussion.
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 discussion on PR #283 and inspect how warnings are emitted when implementing the supported content_render() method through experimental APIs. Trace the warning path in the R package and confirm that removing unsupported API warnings does not affect supported API behavior; done means those warnings are no longer produced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100