potassco / potassco/constraint-handler
naming conventions
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 20
Description
Currently, naming conventions seem to be a bit mixed:
e.g. EvaluateVariable and Multimap_Value
Maybe a decision can be made, checking should be easy using pylint or other tools
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 reviewing the codebase occurrences of EvaluateVariable and Multimap_Value to understand the current naming patterns. Decide on a consistent convention, then investigate whether pylint or another tool can check it. Done means the convention is agreed and automated checking can identify violations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100