`test-word` does not check a name bound with `>>`
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Read tests/test-word.xsl:15 and compare how the parser stores names bound with >> in @local and @name. Update the lint check so a bound helper name is checked, then run the packs/single/test-word/ reproduction and confirm it reports one warning at line 8.
Written by the indexing model from the issue text.
Description
tests/test-word.xsl:15 matches the word "test" in @name only. The parser puts a name bound with >> into @local and writes an auto-name such as a🌵8-4 into @name. So a helper of a test bound with >> is never checked, though the motive names "a helper inside a unit test" explicitly.
Steps to reproduce
On master 8c3474dc6eb341cb4968c8dd299ca2b0dba151c0, a pack in packs/single/test-word/:
sheets:
- /org/eolang/lints/tests/test-word.xsl
defects: 1
input: |
[] > app
42 > @
++> can-work
eq. > @
test-data
1
1 >> test-data
Actual result
No defect.
Expected result
One test-word warning at line 8, as for the same program with 1 > test-data, which is reported.
This is the same cause as #1608: other lints read the name as (@local, @name)[1], e.g. design/broad-scope.xsl:35.
- Dominant language
- Java
- Stars
- 14
- Forks
- 41
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 30
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from objectionary/lints
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
objectionary/lints#1613 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
objectionary/lints#1612 ·
Maintainers usually reply within 2 days
-
`invalid-name-notation` does not check a name bound with `>>`Possibly taken @StanislavKozachenko claimed this 1 day ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/lints#1608 ·
Maintainers usually reply within 2 days
-
`unused-alias` reports an alias that is used only in the type of an atom or a voidPossibly taken @StanislavKozachenko claimed this 1 day ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/lints#1607 ·
Maintainers usually reply within 2 days
-
`comment-is-too-wide` splits a comment at a literal `\n`, so it reports a wrong line or misses a wide onePossibly taken @StanislavKozachenko claimed this 2 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
objectionary/lints#1600 ·
Maintainers usually reply within 2 days
All issues in objectionary/lints
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aws/context-ontology-accelerator#325 ·
Maintainers usually reply within 1 day
-
The README tells to run `mvn jeo:disassemble`, which fails with `No plugin found for prefix 'jeo'`Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
objectionary/jeo-maven-plugin#1938 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oVirt/ovirt-engine#1219 ·
Maintainers usually reply within 1 day
-
pending:code-area pending:issue-category to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
area:core bug priority:p2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aomarai/minecraft-mcp#247 ·
Maintainers usually reply within 1 day