Feature Request: adding custom preprocessor definition

[daniilvinn]

I have a suggestion to make this extension be able to parse custom preprocessor definitions.
Example: in my engine I implemented #stage definition, so I can write all pipeline shader stages in one file, but since it is "unknown preprocessor directive", I have tons of errors by extension's code analyzer.

How I would like to see it: add extension settings menu, which will contain list of custom preprocessor definitions, possibly their values or syntax, so I can write like this: #testmacro <> : <> and extension will understand, that #testmacro has its own syntax.