XPath function name typo silently ignored
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 182
- Forks
- 99
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 8
Description
If a function name is misspelled, REXML::XPath.match doesn't warn or raise.
REXML::XPath.match doc, '//foo[positoin()=1]'
Weird case:
doc = REXML::Document.new('<foo><namae>bar</namae><bar/></foo>')
REXML::XPath.match doc, '//*[namae()="bar"]'
#=> [<foo> ... </>]
Contributor guide
No contributing guide indexed for this repository
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 at REXML::XPath.match, using the misspelled-function examples in the issue to trace how XPath function names are handled. Verify that an unknown function no longer passes silently, and check both the positoin() case and the namae() case for consistent behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100