Repository navigation
Conversation
Replace the manual comment-checking function with a more robust GetContextAtPosition procedure that tracks strings and different types of comments during parsing. This prevents trigger definition lookups while the cursor is inside strings or comment blocks.
|
This approach feels wrong to me in general. Doesn't code tools know where comments and keywords are? That information but be in there somewhere. Maybe have the LLM search in the code tools source and see if it can find anything. |
|
Update checking using CodeTools API. But checks were not successful eventhough i successfully built on my machine and test run without failure |
|
Do we have minimum/maximum requirement version of fpc? I develop this PR using fpc 3.3.1 but Action runner for this repo is run on 3.2.2 which fail to build my PR. I thought "Requires Free Pascal Compiler version 3.2.0 and Lazarus trunk sources." in readme was a minimum requirement
|
|
I think this is better done in upstream. CodeTools should ignore FindDeclaration request on comments and string literals. |
2 participants
Don't call CodeToolBoss.FindMainDeclaration inside comments and strings.
I believe it also fixes #151