IDEs Support (IntelliJ Platform) | JetBrains

Peter Gromov

Total activity 2258
Last activity May 09, 2023 12:44
Member since July 25, 2008 18:59
Following 0 users
Followed by 1 user
Votes 0
Subscriptions 739

Created May 25, 2015 20:14

LookupElement can have several lookup strings (see getAllLookupStrings method). So you can add another lookup string, that just corresponds to the function name.
- 0 votes
Created May 26, 2015 07:21

I've never seen this. org.jetbrains.plugins.groovy.lang.lexer.GroovyTokenTypes#mNLS is a whitespace token with a distinct element type, which seems to be preserved in PSI. Maybe the reason is it pa...
- 0 votes
Created May 26, 2015 09:10

In GroovyParserDefinition.getWhitespaceTokens only TokenType.WHITE_SPACE is returned. mNLS is considered just another token, visible to the parser, with a possibility to have a special PSI wrapper ...
- 0 votes
Created May 26, 2015 09:26

Yes, you need to handle them in the parser.Stub index is also a kind of file-based index. You will probably need stubs, it's perfectly possible to to use them in whatever file the index processes.
- 0 votes
Created May 27, 2015 06:10

You need PairedBraceMatcherAdapter (or a simpler PairedBraceMatcher).
- 0 votes
Created May 29, 2015 05:10

Please try implementing RenameInputValidator
- 0 votes
Created June 23, 2015 12:14

Have you tried TemplatePreprocessor?
- 0 votes
Created June 23, 2015 17:00

To me, it looks like just two identifiers: Foo and Bar. Find Usages will split the name of searched entity anyway using StringUtil#getWordsIn, so you will need to have indexed the same words.
- 0 votes
Created July 19, 2015 21:11

Your parser produced a tree which doesn't correspond to the new document text. It might be caused by incorrect incremental reparse. I'd start debugging in BlockSupportImpl and check how it calls yo...
- 0 votes
Created July 29, 2015 08:55

Most likely it's some issue with incremental lexer-editor-highlighter update. The only way to tell is to reproduce and debug :(
- 0 votes