speced / speced/respec

Support "old ids" for terms that change

Open
#1,716 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature request High priority
Dominant language
JavaScript
Stars
806
Forks
434
Avg merge
1d 21h
Merged PRs (30d)
32

Description

When a term was defined in published spec, but then vanishes from a spec, ReSpec should complain.

This may be because:

  1. the term was deleted
  2. the term was renamed

Related to:
https://github.com/w3c/tr-design/issues/153

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing this issue and the related tr-design issue 153 to understand how ReSpec tracks terms across published specifications. Determine how deleted and renamed terms should be identified and reported; done means ReSpec detects vanished terms and clearly distinguishes those cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.