Ambiguous duplicate definitions
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 806
- Forks
- 434
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 32
Description
Description of problem
There can be instances where a WebRef data contains duplicate definitions:
https://github.com/w3c/webref/issues/780
Right now, ReSpec gets very confused by this (as it's totally unexpected and should never happen... yet, here we are 🫠).
However, it might be possible to gracefully handle this case by checking if the ambiguity is happening in the same spec... and if it is, take the first or last duplicate as ok and just show a warning.
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
No files or tests are named. Start by locating ReSpec's WebRef definition-resolution entry point and reproduce the issue with duplicate definitions in the same specification. Done means same-spec duplicates are handled deterministically and a warning is shown, while ambiguity across specifications remains appropriately handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100