eclipse-xtext / eclipse-xtext/xtext
Parameterised grammar rules can generate wrong method names
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
When using parameterised rules, sometimes, a wrong method name is generated. This rule name is created with information from the generated (Content Assist) parser. The wrong method name leads to a non-existing method name and an exception java.lang.NoSuchMethodException.
More details:
https://github.com/NumberFour/n4js/issues/325
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 with the parameterised grammar-rule behavior and the generated Content Assist parser described in this issue, then review the linked issue #325 for details. Trace how the rule name becomes a generated method name; done means valid method names are generated and the reported java.lang.NoSuchMethodException no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100