Accept opaque identifier and full URI
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 34
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
For example https://github.com/w3c/node-w3capi#users
If I start with w3capi.group(110151).users().fetch() I will get a list of users, now to get affiliations of each user I can't simply iterate with w3capi.user(user.href).affiliations().fetch(), instead I need to extract opaque identifiers from the URI with something like user.href.split('/').pop(). It would be nice if the client checked if URI is being passed and accept them wherever it accepts opaque identifiers.
Contributor guide
No contributing guide indexed for this repository
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 client entry points shown in the example, including group(), user(), users(), and affiliations(), and trace how each accepts an opaque identifier. Exercise the URI example from the issue and verify that full URIs work wherever opaque identifiers are accepted while existing identifier calls continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100