potassco / potassco/constraint-handler
Manually assigning a value to execution_output should give at least a warning
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 20
Description
At the moment there is no warning when the user assigns a value to execution_output (E.g. variable_define(execution_output(...)))
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 tracing the execution_output and variable_define entry points mentioned in the issue to see where a user-assigned value is handled. Done means such an assignment emits at least a warning, with coverage added or updated for the example case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100