potassco / potassco/constraint-handler
More structured warnings
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 20
Description
Warnings should be emitted with predicate warning/3 with the following signature.
warning(Type, Identifiers, Details).
| Name | Description |
|---|---|
Type |
The type of error/warning that was issued. |
Identifiers |
The list of statement identifiers relevant to the warning. |
Details |
Further details. |
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, tests, or entry points are named. Start by searching the repository for existing warning emission code and its tests, then trace every warning path to determine the required changes. Done means warnings consistently use warning/3 with Type, Identifiers, and Details, with the relevant tests passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100