Private and Protected patterns question #2166
-
In my codebase, the convention is to prefix private fields with I would like to get the VSCode extension to be able to recognize this, but I'm having trouble setting up the Using simply Looking at the source I see there's some wrapper script for LPEG being used for the pattern matching - sadly I don't have any experience with it. Is there anything I could do to get these settings working right for my use case? I know it's possible to explicitly annotate fields as private/protected, however I'd like to avoid having to do this manually for all existing classes. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I did figure it out using the Range rule in the grammar in glob.lua: |
Beta Was this translation helpful? Give feedback.
I did figure it out using the Range rule in the grammar in glob.lua: