Unclosed Block Comments Show Wrong Line Number in Error
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
Research direction
Start by finding the parser code that detects unclosed block comments and reports their opening line; the issue does not name a file or test. Reproduce with the two snippets in the report and trace how preceding structures affect the reported line. Done when both examples report the actual line where ### opens, with a regression test covering the cases.
Written by the indexing model from the issue text.
Description
Skript/Server Version
[Skript] Server Version: Paper 26.2 #134 (3e24be0)
[Skript] Skript Version: 2.17.1 (selfbuilt-unknown)
[Skript] Installed Skript Addons:
- skript-reflect v2.6.3 (https://github.com/SkriptLang/skript-reflect)
[Skript] Installed dependencies:
- Vault v1.7.3-b131
Bug Description
###
a
A block comment (###) was opened on line -1 but never closed.
The issue isn't limited to the first line of the file, it can also report "line 1" when there are other structures
on load:
stop
###
a
Expected Behavior
It should display the correct line number in the error
Steps to Reproduce
Errors or Screenshots
No response
Other
No response
Agreement
- I have read the guidelines above and affirm I am following them with this report.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 456
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from SkriptLang/Skript
-
bug priority: lowest
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SkriptLang/Skript#8952 · 1 comment ·
Maintainers usually reply within 1 day
-
Support `glid(e|ing)` in glide toggle eventPossibly taken @AnOwlBe claimed this 200 days ago. Openenhancement priority: lowest suggestion
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
SkriptLang/Skript#8573 · 2 comments ·
Maintainers usually reply within 1 day
-
bug priority: lowest
Difficulty 3/5 1-2 days Newbie friendliness 57/100
SkriptLang/Skript#8954 · 1 comment ·
Maintainers usually reply within 1 day
-
Command BugsPossibly taken @APickledWalrus claimed this today. Openbug PR available priority: medium
SkriptLang/Skript#8936 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Add a Key PropertyOpenpriority: low suggestion
Difficulty 4/5 3-5 days Newbie friendliness 50/100
SkriptLang/Skript#8932 · 1 comment ·
Maintainers usually reply within 1 day
All issues in SkriptLang/Skript
Similar issues
-
jules
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-learning-exchange/myplanet#18568 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
quarkiverse/quarkus-ironjacamar#264 · 7 comments ·
-
[Bug]: Login shows only "Log-in failed" when Commons answers the login request with an API errorOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
commons-app/apps-android-commons#7295 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
hibernate/hibernate-reactive#4485 ·
Maintainers usually reply within 1 day