Validate URLs (in ResourceArray, AtomicURL)
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.6k
- Forks
- 82
- Avg merge
- 10h 34m
- Merged PRs (30d)
- 205
Description
I can currently create ResourceArrays with any string, but this will fail.
- Should we check for valid URLs or any valid URI?
- Should we fetch HTTP(S) URLs and try if they resolve? If it does not resolve, does that mean that the data is invalid?
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 by locating the ResourceArray and AtomicURL definitions in the repository and read how their values are currently accepted. Decide whether validation should cover URLs or all URIs, and whether HTTP(S) resolution is part of validity; done means the chosen policy is implemented and its behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100