increment/decrement raises ruby error when incorrect argument passed
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 11.9k
- Forks
- 1.5k
- Avg merge
- 17h 55m
- Merged PRs (30d)
- 3
Description
The following:
{% increment var %}
{% decrement var %}
will raise a no method error if var is an Array or Hash. We should raise some liquid error instead to indicate it is related to user input but not a liquid bug.
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 locating the implementation and tests for the increment and decrement tags, then reproduce the Array and Hash argument cases described in the issue. Done means those inputs raise an appropriate Liquid error instead of a Ruby NoMethodError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100