Consider supporting GUID input in pin_read() for Connect
Open
Nobody has claimed this yet.
.enhancement
be:rsc
- Dominant language
- Python
- Stars
- 59
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
same as https://github.com/rstudio/pins-r/issues/874 but for Python. It looks like we're already using the content GUID to retrieve bundles from Connect, so we might be most of the way there already
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 pin_read() entry point and compare this issue with rstudio/pins-r#874. Trace how Connect bundle retrieval currently uses the content GUID, then determine the expected GUID input behavior and how it should be verified. The work is done when pin_read() accepts the intended GUID form for Connect and the relevant behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100