Revise terminology in Interactive Configuration API
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The Interactive Configuration API introduced by #5 contains some terminology we want to revise:
- the term "leaf" or "leaf class" is sometimes not used correctly
- complete/partial constraints: this naming is not very clear and could be revised if we have a good idea
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 reading the Interactive Configuration API introduced by #5 and trace where “leaf” or “leaf class” and “complete/partial constraints” are used. Done means the terminology choices are agreed and applied consistently across the affected API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100