`compound-name` 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
- 76/100
Research direction
Start with names/compound-name.xsl:30 and compare how it checks @name with the (@local, @name)[1] pattern used in design/broad-scope.xsl. Reproduce the case in packs/single/compound-name/ and run its lint test; done means the >> bound name produces the expected compound-name warning at line 2.
Written by the indexing model from the issue text.
Description
names/compound-name.xsl:30 checks @name only. The parser puts a name bound with >> into @local and writes an auto-name such as a🌵2-2 into @name. So a compound name of an application bound with >> is never reported, while the same name bound with > is.
Steps to reproduce
On master 8c3474dc6eb341cb4968c8dd299ca2b0dba151c0, a pack in packs/single/compound-name/:
sheets:
- /org/eolang/lints/names/compound-name.xsl
defects:
- severity: warning
line: 2
input: |
[] > app
x.times 2 >> obj-foo
Actual result
No defect.
Expected result
One compound-name warning at line 2, as for foo > obj-foo in catches-compound-kebab-case.yaml, which is reported.
Same cause as #1608 and #1611: other lints read the name as (@local, @name)[1], e.g. design/broad-scope.xsl.
- 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 78/100
objectionary/lints#1611 ·
Maintainers usually reply within 2 days
-
`invalid-name-notation` does not check a name bound with `>>`Possibly taken @StanislavKozachenko claimed this 2 days 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 2 days 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
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 2 days
-
code-health feature/sync OS/Android QA/Test-Plan-Specified QA/Yes
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
brave/brave-browser#60327 ·
Maintainers usually reply within 1 day
-
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
-
effort/l priority/p2 risk/high triage/deferred
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
iflytek/skillhub#1039 · 1 comment ·
Maintainers usually reply within 1 day