Skip to content

Fix false positive "Unresolved BNF References" for methods from GeneratedParserUtilBase if parserUtilClass does not inherit it - #351

Open
Vladislav Rassokhin (VladRassokhin) wants to merge 1 commit into
JetBrains:masterfrom
VladRassokhin:issue-350
Open

Fix false positive "Unresolved BNF References" for methods from GeneratedParserUtilBase if parserUtilClass does not inherit it#351
Vladislav Rassokhin (VladRassokhin) wants to merge 1 commit into
JetBrains:masterfrom
VladRassokhin:issue-350

Conversation

@VladRassokhin

Copy link
Copy Markdown

No description provided.

…ratedParserUtilBase` if `parserUtilClass` does not inherit it

Fixes JetBrains#350
@gregsh

Copy link
Copy Markdown
Collaborator

Let's process parser imports correctly. The patch is rather a hack to support that particular single case.

General fix:

Get all parser imports (no semicolons, btw), and cycle through static fqn.* and fqn.method entries.

Funny, but quoted idents with dots are not properly generated, so we can skip fqn imports.
Or they too can be supported, because <<<GeneratedParserUtilBase.eof>>> could work 😄 .

That's it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants